List quotes

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

Describes read-only listing with included details (totals, validity, verdicts), but provides no information on default status filter, pagination, ordering, or authentication. With no annotations, more detail would improve 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?

Single sentence that is clear, efficient, and front-loaded with essential information. No redundant words.

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?

For a simple list tool with one parameter and no output schema, the description covers purpose, optional filtering, and key output fields. Lacks details on ordering or limits, but is adequate given the tool's simplicity.

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 0%, but description adds meaning by stating 'optionally filtered by status', clarifying the parameter's optional nature and role. The enum values are documented in the schema, so this is sufficient.

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?

Clearly states 'List quotes' with optional status filtering and mentions output includes totals, validity, and profitability verdicts. Distinguishes from siblings like quote_create and quote_update_status, but could better differentiate from other list tools like pipeline_view.

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?

Implies usage for listing quotes with optional status filter, but lacks explicit guidance on when to use this tool versus alternatives like quote_price or quote_render.

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