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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is clear. The description adds useful behavioral context by describing what data is returned: client/prospect, totals, and line items. It stops short of covering error behavior or authorization details, which is acceptable given the simple read-only nature.

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 compact sentences with no filler. The core return content is front-loaded, followed by the endpoint reference, making it easy to scan.

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 single-parameter read tool with full schema coverage and clear annotations, the description provides enough context: it specifies the resource, identifies the parameter type through the schema, and summarizes the returned data. No output schema exists, but the description sufficiently communicates the key return contents.

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%, and the quote_id parameter is documented as a GUID returned by list tools. The description does not add meaning beyond the schema, but the schema already handles parameter semantics adequately, so the baseline of 3 is appropriate.

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 uses a specific verb-resource pair, 'Get quote', and states the returned content: a single quote with client or prospect, totals, and line items. It implicitly distinguishes itself from list_quotes by saying 'One quote', but does not explicitly name the sibling or contrast the use cases.

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?

Usage is implied by the operation: retrieve one quote by id. However, the description does not explicitly say when to use this instead of list_quotes or other quote-related tools, nor does it state any preconditions or exclusions.

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