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

With no annotations, the description must disclose behavior, but it only lists the draft's contents. It does not state that the tool is a read-only retrieval, whether permissions are required, or what happens if the draft ID is invalid or missing.

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 a single sentence with no obvious filler, but it is a sentence fragment that front-loads a noun instead of the action. The list of draft fields is dense but not wasteful, though the missing verb weakens its immediate 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?

Given the absence of annotations, an undocumented required UUID parameter, and an output schema that already covers return values, the description is incomplete. It should at minimum state that the tool retrieves a quote draft by ID and explain the parameter, but it only describes the draft's 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?

The single required parameter, draft_id, has 0% schema description coverage, and the description never mentions it. It does not explain that the UUID identifies which quote draft to retrieve, so it fails to compensate for the schema 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?

The description is a noun phrase that restates the tool name and lists draft contents rather than stating an action verb. It never says whether this retrieves, creates, or updates a quote draft, so it does not distinguish the tool from siblings like quotes_finishDraft or quotes_decideDraftLine.

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?

No guidance is given about when to call this tool instead of related siblings such as quotes_decideDraftLine, quotes_finishDraft, or quotes_draftFromVisit. The description also omits any prerequisites or context for use.

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