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

Annotations already declare the safety profile (readOnlyHint=false, idempotentHint=true, openWorldHint=true), but the description adds real side-effect detail: a message goes to the sales team, a receipt email reaches the buyer, and attachment links are downloaded and stored privately. It does not cover failure modes (invalid/expired token, partial send) or what a successful response looks like, so it is strong but not exhaustive.

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?

Four short sentences, front-loaded with the step position and the action, then the precondition, then the attachment caveat. Every sentence carries a distinct piece of information with no repetition of the schema.

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, 5-required mutation with no output schema and external side effects, the description covers purpose, prerequisite, data-consistency requirement, and attachment handling. It stops short of describing error behavior (bad token, download failure) or confirming what the return value signifies.

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%, so the baseline is 3. The description goes beyond the schema by tying confirmation_token to a specific producer ('the confirmation_token preview_inquiry returned') and imposing a cross-field constraint — all fields must match the previewed summary exactly — which no individual property description expresses.

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 second observable effect ('emails the buyer a receipt'). Labeling itself 'Step 2 of 2' and naming preview_inquiry as the step-1 counterpart cleanly separates it from that sibling.

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?

Gives an explicit precondition ('only after the buyer explicitly confirmed the preview_inquiry summary'), names the gating tool, and specifies the required data continuity ('exactly the same fields and its confirmation_token'). An agent knows precisely 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.