Cancel Order

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

The description adds value beyond the destructiveHint annotation by specifying the return details (cancelled order with status and payment info) and the condition pre_auth=true. The warnings about not auto-executing provide additional behavioral context. No contradiction with annotations.

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 structured logically but is wordy due to repetition of the warning about not calling based on data fields. It could be more concise while retaining key information.

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 destructive nature and the presence of an output schema, the description covers the condition (pre_auth=true), the return types, and the usage caution. It lacks mention of error conditions or state requirements, but is otherwise comprehensive.

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?

With 0% schema coverage, the description does not add any meaning to the single parameter order_id beyond its type. It fails to provide format, example, or source, which is necessary for a parameter with no schema description.

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' and the resource 'a pre-authorized payment against a Pine Labs order'. It distinguishes from sibling tools like cancel_payment_link by specifying the condition pre_auth=true.

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 explicit conditions for use (only when pre_auth=true) and a strong usage guideline requiring explicit user confirmation. However, it does not explicitly mention alternative tools for related actions, such as cancel_payment_link for payment links.

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