dbt-list-macros

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

With no annotations, the description carries full burden. It states the tool reads from 'manifest.json' and applies filters, implying a read-only operation. However, it does not disclose auth requirements, whether it accesses local files or remote endpoints, or the treatment of the default limit parameter. The core behavior is adequately communicated but not thoroughly.

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, short sentence that conveys the essential information without any superfluous words or tangential details. 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?

Given the tool's low complexity (4 params, no output schema, no required params) and the presence of well-described siblings, the description covers the primary behavioral aspects: what it lists, the source, and available filters. It is nearly complete, though it could mention the default limit or how results are ordered. Still, it meets the needs for a simple list 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 adds context (source from manifest.json, filter types) beyond the schema, which already provides descriptions for 3 of 4 parameters. The semantic value is moderate: it clarifies the purpose of search and package filters but omits any mention of the 'limit' parameter, whose schema lacks a description. Overall, it adds some meaning but not deeply.

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 action ('List'), the resource ('dbt macros'), the source ('manifest.json'), and available filters ('package / name'). This effectively distinguishes it from sibling tools like dbt-list-models, which list different resources.

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 vs alternatives (e.g., dbt-get-macro for a single macro, or other list tools). The description does not include when or when not to use it, nor does it reference prerequisites or behavior under different conditions.

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