meican_cancel_order

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

The description correctly notes the destructive nature ('this removes the order'), but without annotations, it should also disclose potential side effects, authorization requirements, or failure conditions. The missing output schema leaves the return behavior ambiguous.

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 highly concise, using only three short sentences to convey purpose, destructiveness, and usage caution. It front-loads the essential information without unnecessary detail.

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 tool with 5 parameters, 1 required, and no output schema, the description is somewhat incomplete. It explains the core action and a key usage constraint but omits response details and the meaning of parameters like 'type', reducing overall completeness.

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 description adds no parameter-specific information beyond what the input schema provides. The required 'order_unique_id' parameter lacks a schema description, and the tool description does not clarify its meaning or format. Schema coverage is 60%, so the description should compensate but fails to do so.

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 'Cancel a meal order' with a specific verb and object, and the 'DESTRUCTIVE' warning reinforces the action. It distinctly differentiates from sibling tools like meican_list_orders and meican_place_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?

The description includes an explicit instruction to 'ALWAYS confirm with the user before calling,' providing clear context for when to invoke the tool. However, it does not mention when not to use it or suggest alternatives for handling cancellation scenarios.

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