cancel_crypto_payment

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

No annotations provided; description only states the valid status for cancellation. Does not disclose irreversible nature, authentication needs, rate limits, or what happens if status is not 'new'. This is minimal 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?

One sentence, front-loaded with purpose and condition. No redundant information, perfectly 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 one parameter and no output schema, the description covers the essential behavior and constraint. Lacks error handling or return value info, but is adequate given low complexity.

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% with a description for the single parameter. The tool description adds no extra meaning beyond the schema, so it meets the baseline without additional value.

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?

Description clearly states the verb (cancel) and resource (pending crypto payment order), and specifies a status condition. It implicitly differentiates from siblings like create_crypto_payment and check_crypto_payment_status, but does not explicitly mention alternatives.

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?

Provides a specific condition for usage (only orders with 'new' status can be canceled), but does not include when not to use or reference alternative tools like check_crypto_payment_status for verifying order state.

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