list_vault_decisions

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

No annotations exist, so the description must disclose behavioral traits. It mentions the data source (dbt mart) and optional filters, but omits details like pagination, sorting, side effects, or data volume expectations. The description is too minimal to convey 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?

The description is a single, front-loaded sentence. It is concise (10 words) and immediately conveys purpose. However, it could include more detail without losing conciseness.

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?

With 5 parameters (1 required) and an output schema, the description should provide more context about what decisions are, how filters work, or any constraints. It lacks completeness, leaving the agent with only the schema to interpret behavior.

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 description coverage is 100%, so the baseline is 3. The description aligns with 'entity' and 'status' parameters as optional filters, but does not add new meaning beyond what the schema already provides. The mention of 'dbt mart-backed' gives context but not for specific parameters.

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 it lists decisions from a dbt mart with optional filters. It is specific about the resource (decisions) and source (dbt mart), but does not explicitly differentiate from sibling list tools like list_vault_entity_events or list_vault_entity_open_loops.

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. The description only mentions optional filters, leaving the agent to infer usage context from the name and schema alone.

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