List Quotes

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

Annotations already indicate read-only, non-destructive, idempotent, and open-world behavior. The description adds value by detailing OData capabilities (filter, sort, pagination) and a specific expand usage for custom fields. There is no contradiction with annotations.

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 sentences, front-loaded with the main purpose. No redundant words; every phrase adds value. The structure efficiently communicates the tool's function and key features.

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 no output schema, the description could mention that it returns a list of quotes, but the title implies this. It adequately covers input parameters and OData operations. It is complete enough for a simple list tool with well-annotated schema.

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 provides an additional usage tip for the expand parameter ('Use $expand=OtherProperties to include custom fields'), adding meaning beyond the schema's list of entities.

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 ('Search and list'), the resource ('quotes (proposals)'), and the system ('Ploomes CRM'). It distinguishes from sibling list tools by specifying 'quotes' and mentions key features like OData filtering, sorting, field selection, and pagination.

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 provides clear context on when to use the tool: for searching and listing quotes. It explicitly mentions supported OData operations and a specific expand hint. However, it does not exclude scenarios or compare to other quote-related tools (create, get, update, delete), which are present as siblings.

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