cancel_order

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

The description notes the tool modifies state (cancels an order) but does not disclose side effects, such as what happens to related entities (e.g., positions) or whether cancellation is irreversible. With no annotations, the description should provide more behavioral 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 extremely concise, consisting of just three words. While brevity is valued, it comes at the cost of clarity and completeness, making it minimally acceptable.

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?

The tool has one parameter, no output schema, and no annotations, yet the description does not explain the cancellation process, return value, or error conditions. It is too sparse to fully guide an AI agent.

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?

The only parameter, order_id, has a title 'Order Id' in the schema but the description adds no further explanation. Given 0% schema description coverage, the description fails to clarify the parameter's format, constraints, or source.

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 clearly states the action (cancel) and resource (order), making the tool's purpose immediately understandable. However, it does not differentiate from other cancellation tools, though sibling tools like delete_pie target different resources.

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?

No guidance is provided on when to use this tool versus alternatives like place_order or fetch_all_orders. There is no mention of prerequisites (e.g., order must be in a cancellable state) or exclusions.

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