Cancel an unpaid EMC order

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

Describes destruction (expiring, freeing slot), error on late payment, and consequence of no refund. Annotations already indicate destructiveHint=true, but description adds valuable context beyond annotations.

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 sentences with no wasted words. First sentence states core action and effect. Subsequent sentences provide timing constraints, error condition, and alternative tool. Efficient and well-structured.

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 single-parameter tool with output schema present, description gives complete behavioral context: what it does, when to use, error cases, consequence of misuse, and alternative. No gaps.

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% for the single token parameter. Description only references the token generically, adding no new semantics beyond what the schema already provides for the parameter.

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?

Description clearly states the tool cancels an unpaid buy_emc order by token, expiring it and freeing its slot. It distinguishes from sibling get_order_status, which is for inspection only.

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 states to use only before payment, with clear error condition if too late. Mentions alternative get_order_status for inspection. Does not contrast against buy_emc or get_swap_config, but coverage is adequate.

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