Add specificity to tool descriptions to delineate

Author: VDFaller

src/dbt_mcp/prompts/dbt_cli/get_model_lineage_dev.md

@@ -1,2 +1,26 @@
-This tool retrieves the lineage of a specified dbt model in the local development environment.
+get_model_lineage_dev
 
+<instructions>
+Retrieves the model lineage of a specific dbt model, it allows for upstream, downstream, or both. These are the models that depend on the specified model.
+
+You can provide either a model_name or a uniqueId, if known, to identify the model. Using uniqueId is more precise and guarantees a unique match, which is especially useful when models might have the same name in different projects.
+This specifically ONLY pulls from the local development manifest.  If you want production lineage, use `get_model_children` or `get_model_parents` instead.
+</instructions>
+
+<parameters>
+model_id: str => Either the uniqueId or the `identifier` of the dbt model to retrieve lineage for.
+direction: Literal["parents", "children", "both"] = "both"  => The direction of lineage to retrieve. "parents" for upstream models, "children" for downstream models, and "both" for both directions.
+exclude_prefixes: tuple[str, ...] = ("test.", "unit_test."), => A tuple of prefixes to exclude from the lineage results. Assets with identifiers starting with any of these prefixes will be ignored.
+recursive: bool = False => Whether to retrieve lineage recursively. If set to True, it will fetch all levels of lineage in the specified direction(s).
+</parameters>
+
+<examples>
+1. Getting children for a model by name:
+   get_model_lineage_dev(model_id="customer_orders", direction="children")
+
+2. Getting parents for a model by uniqueId (more precise):
+   get_model_lineage_dev(model_id="model.my_project.customer_orders", direction="parents")
+
+3. Getting both upstream and downstream lineage recursively and including tests:
+   get_model_lineage_dev(model_id="model.my_project.customer_orders", direction="both", exclude_prefixes=(), recursive=True)
+</examples>

src/dbt_mcp/prompts/discovery/get_model_children.md

@@ -2,6 +2,8 @@
 Retrieves the child models (downstream dependencies) of a specific dbt model. These are the models that depend on the specified model.
 
 You can provide either a model_name or a uniqueId, if known, to identify the model. Using uniqueId is more precise and guarantees a unique match, which is especially useful when models might have the same name in different projects.
+
+This is specifically for retrieving model children from the production manifest. If you want development lineage, use `get_model_lineage_dev` instead.
 </instructions>
 
 <parameters>

src/dbt_mcp/prompts/discovery/get_model_parents.md

@@ -4,6 +4,8 @@ Retrieves the parent models of a specific dbt model. These are the models that t
 You can provide either a model_name or a uniqueId, if known, to identify the model. Using uniqueId is more precise and guarantees a unique match, which is especially useful when models might have the same name in different projects.
 
 Returned parents include `resourceType`, `name`, and `description`. For upstream sources, also provide `sourceName` and `uniqueId` so lineage can be linked back via `get_all_sources`.
+
+This is specifically for retrieving model parents from the production manifest. If you want development lineage, use `get_model_lineage_dev` instead.
 </instructions>
 
 <parameters>