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

Annotations already declare not-read-only, open-world side effects and idempotency, so the bar is lower; the description still adds real value by disclosing the outbound email receipt and that attachment links are downloaded and stored privately. It does not address what happens on duplicate or failed submission, which would matter given idempotentHint=true.

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?

Three short sentences, zero waste, with the sequencing and precondition front-loaded before the side effects.

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 an 11-parameter mutation with no output schema, the description covers the gating flow and the observable outcome (sales team notification, buyer receipt, private attachment storage). It stops short of describing failure/retry behavior or what a returned confirmation looks like, which the absent output schema forces the agent to guess.

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% with per-field descriptions, so the schema does the heavy lifting. The description only reinforces that field values must be identical to the preview_inquiry payload and that confirmation_token must be carried over — useful but marginal.

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 (sends the confirmed quote request to the HLN sales team) plus a secondary effect (emails the buyer a receipt). The 'Step 2 of 2' framing and the reference to preview_inquiry make it unmistakable which sibling precedes it.

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?

Names the explicit gating condition — only after the buyer confirmed the preview_inquiry summary — and adds the data-consistency requirement (same fields, same confirmation_token). An agent knows exactly when to call this and when not to.

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