cancel_order

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

No annotations provided, so description fully carries the burden. Explicitly states it is a WRITE operation ('cancels a live order') and highlights the environment variable requirement. Also clarifies it does not affect filled portions.

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 redundancy. Each sentence contributes critical information: action, effect on filled portions, alternative for TWAP, and side effect/requirement. Perfectly front-loaded.

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?

Given the tool has only one parameter, no output schema, and no annotations, the description covers all essential aspects: operation, scope, limitations, alternatives, and prerequisites. No gaps for an AI agent to use it correctly.

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 has 0% description coverage. The description mentions 'by orderId', giving context that the parameter identifies the order. However, lacks additional details like format or where to obtain the orderId. Still adds meaning beyond the raw 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?

Clearly states it cancels pending Pear Protocol orders (limit, take-profit, stop-loss) by orderId. Distinguishes itself from sibling cancel_twap_order by explicitly saying 'For TWAP orders, use cancel_twap_order'.

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?

Provides explicit when-to-use (cancelling limit, TP, SL orders) and when-not-to-use (TWAP orders). Also notes that already-filled portions are not affected and requires PEAR_TRADE_ENABLED=true.

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