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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered elsewhere. The description adds the meaningful behavioral fact that only unsent drafts are returned — a real filter, not a restatement — but says nothing about ordering, pagination, or result size limits for a list operation.

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?

A single front-loaded sentence with the core constraint ('not sent yet') first and the optional filter second; nothing is wasted. It is terse to the point of reading as a noun phrase rather than an instruction, but that costs no clarity.

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 one-parameter, zero-required read tool with full schema coverage, complete annotations, and no output schema, the description covers the essential scope and filter behavior. The only gaps are return ordering and pagination for what is presumably a list result, which are minor at this complexity.

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 100%, and the schema itself explains that customerName accepts a name or company and is optional. The description restates the optionality without adding format, matching, or partial-match semantics beyond what the schema already provides, so baseline 3 applies.

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 names the resource precisely ('quote drafts that have not been sent yet') and the optional narrowing filter, so an agent knows exactly what set is returned. It implicitly distinguishes itself from listQuotes by restricting to unsent drafts, though it never states that contrast explicitly.

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 resource definition: retrieve unsent drafts, optionally scoped to one customer. There is no explicit when-to-use versus listQuotes or fetchQuoteHistory, and no when-not guidance, leaving the agent to infer the boundary from names.

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