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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds genuinely new behavior: no charge or submission occurs, completed quotes are terminal, access is scoped to account/endpoint/environment, and guest IDs are bearer capabilities. The guest-ID sentence is a bit cryptic and its relation to quoteId is left implicit.

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?

Five short sentences, front-loaded with what is read and what is returned. The final two sentences are terse to the point of being under-explained, but no sentence is filler.

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?

An output schema exists, so return values need not be spelled out, and the safety profile is covered by annotations. What remains covered is the charge/submission guarantee and terminal-state rule; only the quoteId origin is missing.

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 0% for the single required quoteId, so the description must carry the load. It gestures at identifier semantics ('Guest IDs are private bearer capabilities', access bound to account/endpoint/environment) but never says what quoteId is or where to obtain it, leaving a real gap.

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?

States a specific verb and resource ('Read a saved standard-mail quote') and even enumerates what is returned (exact PDF and send outcome). It does not explicitly contrast itself with siblings like quote_letter or send_letter, but the read-of-saved-quote framing is 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?

'Use after interruption' gives a concrete triggering situation, and 'completed quotes cannot be sent again' tells the agent a hard precondition on downstream action. No sibling is named as an alternative, so it stops short of full routing guidance.

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