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

Annotations already declare destructiveHint=true and openWorldHint=true; the description adds critical context beyond that: design data is published to a third party, the call is gated on explicit user request, and the return is a payment page. It also flags that some providers require shipping. This is exactly the extra context the annotations cannot carry.

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, front-loaded with the action and outcome, followed by the gating condition and a provider-specific caveat. No filler.

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 destructive, open-world mutation with no output schema, the description covers what is sent, who receives it, the precondition, and what is returned (payment page). The only minor omission is error behavior on unsupported providers, but overall it is complete enough to invoke safely.

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 baseline is 3, but the description adds meaning: user_confirmed is tied to explicit user intent (beyond the schema's const:true), provider references list_order_providers, and shipping is conditional. It doesn't cover title or boards, but those are well-documented in the schema.

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?

Specific verb and resource ('Upload the released board ... to a manufacturer and return the page where the user pays') immediately distinguishes it from siblings like upload_board or get_order_price. The scope — publishing Gerbers, BOM, placement to a third party and handing off to a payment page — is clear.

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?

Explicitly says 'call it only when the user has explicitly asked to order from that provider, and set user_confirmed only then', and notes the shipping-address condition. This names the precondition and the confirmation requirement that select this tool over get_order_price or list_order_providers.

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