list_decisions

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

No annotations are present, so the description must carry the full burden. It only says 'List' without disclosing that it requires authentication, supports date range filtering, pagination through limit/offset, or what the return format is. The read-only nature is inferred from the verb but not explicitly stated.

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?

Two short sentences that state the core function and intended use. No redundant information; front-loaded with the action.

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 adequate for a basic list operation, but given five parameters including pagination and date ranges, it does not explain how the optional parameters affect results. It also does not distinguish from get_decision for single retrieval, which would help contextual placement.

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%, with descriptions for to, from, limit, offset, and auth_token. The description adds no information about these parameters or how they relate to the listing behavior.

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' and the resource 'your decision records', distinguishing it from get_decision which retrieves a single record. The added phrase 'See the trajectory you have built so far' reinforces the purpose.

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?

The description implies usage for reviewing historical decisions, but it does not explicitly state when to use this tool versus alternatives like get_decision or get_decision_metadata_distribution. No exclusions or alternative guidance is provided.

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