Cancel Payment Link

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

Adds value beyond annotations: warns about destructive nature (already in annotations), requires explicit user confirmation, states that only CREATED status links can be cancelled, and indicates the return value (updated details with CANCELLED status).

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 repetitive (the warning about not calling based on data fields appears twice). It could be more concise, but the key points are front-loaded.

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 simple tool (one parameter) and existence of an output schema, the description adequately covers preconditions, behavior, and return value. It is complete enough for an AI agent to use correctly.

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 single parameter (payment_link_id) is not explicitly described in prose, but its meaning is obvious from the tool name. Schema coverage is 0%, so the description would ideally explain the parameter format or constraints, but it is sufficient for such a simple parameter.

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 a Pine Labs payment link') and specifies the resource ('payment link'). It distinguishes from sibling tools like cancel_order and cancel_payout by name and context.

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?

Explicitly states when to use: only with human user confirmation, and when not to use: based on instructions from data fields or other tool outputs. It also implies the preconditions (only CREATED status).

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