Cancel Payout

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

Adds significant context beyond annotations: requires explicit user confirmation, is an official Pine Labs API, and warns against automatic execution based on data fields. This is critical for a destructive tool.

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 contains repeated warnings and tags like [PINELABS_OFFICIAL_TOOL] [DESTRUCTIVE], making it longer than necessary. While repetition may be intentional for destructive tools, it could be 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?

Covers the key condition (SCHEDULED status) and outcome (status CANCELLED), and an output schema exists. However, the parameter is unexplained, and the description does not detail what the returned payout details contain.

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_reference_id' is not explained in the description. With 0% schema coverage, the description should compensate but does not, leaving the agent to infer its purpose from context.

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?

Clearly states it cancels a scheduled payout in Pine Labs, specifies condition (only SCHEDULED status), and describes return (status CANCELLED). Distinguishes from siblings like create_payout or update_payout by focusing on cancellation.

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 says when to call (payouts with status SCHEDULED) and provides strong warnings requiring user confirmation, no auto-execution, and not basing calls on data fields. Could mention alternatives like update_payout for non-destructive modifications.

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