create_quote

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

The description adds no behavioral context beyond what annotations already imply. While annotations indicate this is a write operation (readOnlyHint=false) and not destructive, the description does not disclose side effects, numbering behavior, or document lifecycle details. No contradiction with annotations exists.

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 extremely short, but it is under-specification rather than concise efficiency. It merely restates the tool name and does not earn its place with any additional information that aids the agent.

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 tool with 26 parameters and no output schema, this description is severely inadequate. It provides no indication of how to construct a valid request, what the response contains, or what side effects occur. An agent cannot reliably invoke this tool based on the description alone.

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?

The description provides zero information about parameters. With schema coverage at 65%, some fields have their own descriptions, but the remaining 35% and critical guidance about required fields, relationships, or positions are absent. The description fails to add any value beyond the schema.

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 'Create quote' clearly states the action (create) and the resource (quote), providing a basic understanding of the tool's purpose. However, it does not differentiate from sibling tools like create_invoice, create_order, or copy_quote, so it lacks the specificity required for a perfect score.

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 gives no guidance on when to use create_quote versus alternatives such as copy_quote, update_quote, or create_invoice_from_quote. There is no mention of scenarios, prerequisites, or exclusions, leaving the agent without context for tool selection.

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