cancel_order_by_client_id

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

With no annotations provided, the description carries the full burden of disclosing behavioral traits, but it only states the basic action. It does not mention whether the operation is idempotent, what happens if the order is already canceled, or any permission requirements, leaving significant gaps for safe invocation.

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 short and front-loaded, with no wasted words. However, it could be slightly more informative without sacrificing conciseness, e.g., by mentioning the effect or return value. Still, it is efficient for a simple cancellation tool.

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 lack of output schema and annotations, the description is minimal and does not explain return values, error handling, or prerequisites. For a cancellation operation with multiple sibling tools, the description should provide more context to fully guide usage.

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 schema coverage is 100%, with the parameter 'client_order_id' already described as 'Client order ID to cancel' in the schema. The description adds no additional semantic detail beyond what the schema provides, so a baseline score of 3 is appropriate.

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 verb 'Cancel', the resource 'order', and the method 'by client order ID'. It effectively distinguishes from sibling tools like 'cancel_order' (which likely uses system order ID) and 'cancel_algo_order_by_client_id' (for algo orders), making the tool's purpose specific and unambiguous.

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 its siblings, such as 'cancel_order' or 'cancel_algo_order_by_client_id'. The description lacks explicit context for choosing this tool over alternatives, leaving the agent to infer usage from the name alone.

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