tiendanube_cancel_order

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

With no annotations, the description discloses key behaviors: sets status to 'cancelled' and may trigger automatic refunds based on payment status. It doesn't mention irreversibility or authorization requirements, but provides useful 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 three sentences, front-loaded with an icon and action phrase. It is clear and efficient, though it could be slightly more concise.

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 simple tool with 2 parameters and no output schema, the description covers purpose, usage scenarios, and behavioral effects. However, it omits details like potential side effects (e.g., whether it can be undone) and authorization needs, leaving minor 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%, so the baseline is 3. The description mentions the optional reason parameter but adds no additional meaning beyond the schema's description ('Reason for cancellation').

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 tool cancels an existing order, with an optional reason. It distinguishes from sibling tools like close_order and reopen_order by explicitly using 'cancel' and listing cancellation reasons, though it doesn't directly compare with similar tools.

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 provides when to use the tool (e.g., customer requests, fraud, inventory issues) but lacks explicit guidance on when not to use it or mention of alternatives like close_order or update_order.

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