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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, and the description adds real context on top: the validation rules mirrored from create_order, the contents of the response, the recapRef handoff, and the conflict-on-mismatch consequence. It doesn't say whether generating a recap has side effects on stored state, but the safety profile is well covered.

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 content is dense and mostly earns its place, but it is delivered as one long run-on with a metaphorical opener ('the last thing before the exits') and a cryptic trailing fragment ('Key required'). Front-loading the core function ahead of the validation inventory would make it easier to scan.

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 10-parameter tool with a nested address object and no output schema, the description explains what comes back and how the result feeds create_order, while annotations cover safety. Remaining gaps are the unclear 'required notes' and the unexplained 'Key required' note.

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 description coverage is 100%, so the baseline is 3. The description restates the quantity range, size choices, mounting options, and complete-address requirement that the schema already documents, and it adds only a little (the recapRef round-trip). The phrase 'both required notes' is ambiguous about which of contactEmail/contactName/contactPhone is actually mandated.

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 a concrete operation: it validates the exact order inputs that create_order will carry and returns a recap (artwork, quantity, address, cost, notes, recapRef). The relationship to create_order and get_quote is spelled out, so an agent can distinguish it from every sibling without opening a schema.

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?

It clearly positions the tool as the final step before the exits and states that create_order carries the returned recapRef, with a conflict refusal if inputs diverge — that pins down sequencing and prerequisites. It stops short of an explicit 'call this before create_order instead of X' instruction, so a 4 rather than a 5.

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