dbt-list-exposures

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

The description only states the purpose, not behavioral details like read-only nature, pagination, or performance. With no annotations, the agent lacks context on what side effects or constraints exist beyond the input schema.

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?

A single, well-structured sentence convey the purpose and clarifies the resource type without any fluff. It is front-loaded and efficient.

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?

The description is minimal; it does not mention return value format, filter behavior, or error conditions. Given no output schema and the tool's simplicity, it is adequate but not complete for an agent unfamiliar with dbt exposures.

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?

The description adds no extra meaning beyond the input schema. The schema already provides descriptions for exposureType (enum-like), search, and limit with defaults, so the description is merely redundant. Schema coverage is 67%, but the missing 33% is minor.

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?

The description clearly states 'List dbt exposures' with a specific resource type, and the parenthetical mentions downstream consumers, distinguishing it from siblings like dbt-list-models or dbt-list-sources.

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 explicit guidance on when to use this tool versus alternatives. While the description implies it's for listing exposures, it does not provide exclusion criteria or comparisons to other list tools, leaving the agent to infer usage from the tool name alone.

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