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

Beyond the destructiveHint and idempotentHint annotations, the description explains concrete outcomes: delivered rows remain available, the order settles as partial, the undelivered share is refunded pro rata to the original payment method, and the person is emailed. It also instructs the agent to tell the person the refund amount shown in collection.refund first, which is operationally important context.

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 description is dense but front-loaded with the explicit-use condition, then states the key side effects and the refund-message instruction. Every sentence carries actionable information without repetition.

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, idempotent cancellation tool with no output schema, the description covers the trigger condition, required order status, side effects, refund behavior, and user notification well. The main gap is that it leaves order_capability and idempotency_key semantics unaddressed despite low schema coverage.

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 only 33%, and the description does not explain order_capability or idempotency_key. It provides useful order state context around order_id, but it does not compensate for the undocumented parameters.

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 uses a specific verb and resource: stop continued collection of a guaranteed-N order whose get_order status is collecting. It also states the required order state, making the tool's purpose distinguishable from siblings such as get_order or cancel_request.

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?

The description gives a clear gating condition: only when the person explicitly asks, and only when the order status is collecting. It does not name an alternative sibling tool or spell out when-not cases beyond the prerequisite status, so it falls short of full alternative routing guidance.

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