dbt-get-model

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Description mentions response contents but does not disclose additional behavioral traits such as read-only nature, authorization needs, or rate limits. No annotations provided, so description carries full burden but provides moderate transparency.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

Single sentence efficiently conveys purpose and response contents. Every word adds value; no redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Four parameters well-described, but no output schema and no annotations. Description explains what the tool returns (refs, sources, etc.) but lacks details on error handling, prerequisites, or response format. Given complexity, it is mostly complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema has 100% coverage with descriptions for all 4 parameters. The description does not add significant meaning beyond schema, but the overall context helps interpret parameter purpose. Baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

Description clearly states verb 'Get', resource 'single dbt model', and enumerates included elements (refs, sources, columns, tests, SQL). This distinguishes it from sibling tools like dbt-list-models and dbt-get-source.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool versus alternatives. Implicit from name and sibling tools that it is for fetching one model, but no explicit when-not-to-use or prerequisite information.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.