List Quotes

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true. The description adds that it lists resources and supports filtering/pagination, which is consistent. However, it does not disclose additional behavioral traits like rate limits, authentication needs, or result set handling beyond the implicit pagination.

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 two sentences in English plus a Spanish translation, with no filler. It is front-loaded with the action and includes a concrete example. Every word earns its place.

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 9 parameters (0 required), 100% schema coverage, and an output schema present, the description is reasonably complete. It covers the core functionality and gives an example. It could mention cursor-based pagination or describe the output structure, but overall it provides sufficient context for an AI agent.

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 coverage is 100% with each parameter described. The description adds a high-level statement about filtering by status and date range but does not detail each parameter. Baseline is 3 because schema already covers semantics; description does not significantly enhance parameter understanding.

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 'all quotes/estimates' with filtering and pagination. It distinguishes itself from siblings by naming the resource (quotes) and explaining they are proposals before invoices. This is specific and unambiguous.

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 explains when to use the tool (to list quotes) and provides an example with status and date filters. It does not explicitly contrast with sibling tools like 'search_invoices' or 'list_invoices', but the context of quotes vs invoices is clear. The example aids practical usage.

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