dbt-list-tests

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

No annotations are provided, so the description carries full burden. It only states the action ('list') without disclosing side effects, pagination, rate limits, or any behavioral traits. The limit parameter suggests pagination but is not explained.

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?

The description is a single clear sentence without redundant information. It is concise and front-loaded. However, it could be slightly more structured (e.g., listing parameters or use cases) without adding length.

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?

Given 5 parameters, no output schema, and no annotations, the description is insufficient. It does not explain return value structure, pagination behavior, or how to effectively use the 'extractFields' parameter. Sibling tools are not differentiated, leaving the agent confused about when to use this tool.

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 does not add meaning beyond the input schema. With 60% schema description coverage, the description should compensate for missing parameter explanations, but it does not elaborate on any parameter. The 'extractFields' parameter, which is crucial for token reduction, is not mentioned.

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 the verb 'list', the resource 'dbt tests', and specifies that it can be filtered by test kind (generic, singular) and optionally to a specific model, distinguishing it from sibling tools like dbt-list-models or dbt-get-test.

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 is provided on when to use this tool versus alternatives like dbt-get-test for single test details or dbt-list-models for models. The description does not mention prerequisites, limitations, or which tool to prefer under different scenarios.

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