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

Annotations already declare destructiveHint=true and idempotentHint=true, but the description adds real context beyond them: the pickup cutoff that makes the call fail, the fallback return flow, and the reassurance that the saved card is not charged. It also states the returned state, which matters for a mutation with no output schema.

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 tight sentences, with the core action and the blocking precondition front-loaded. No filler; each clause carries a distinct operational fact.

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?

With no output schema, the description covers the return value ('new state', card-not-charged confirmation) and the failure path, which is what an agent needs. The one gap is the slight mismatch over whether email is mandatory, left unresolved between description and schema.

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 schema already documents all three parameters, and the baseline is 3. The description's 'requires the order code and the email' mildly conflicts with the schema, where only orderCode is required and email is waived for connected accounts — a nuance an agent could misread rather than one the description clarifies.

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 ('Cancel a Fold order') with no ambiguity, and is clearly separable from siblings like reschedule_order, rate_order and list_my_orders. An agent can identify the operation without opening the 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?

Explicitly bounds usage: allowed only before driver pickup, and after pickup the correct path is a return plus a support call. This names both the precondition and the alternative when the precondition fails, leaving little to inference.

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