payway_close_transaction

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

States the outcome (sets status to CANCELLED) and a key side effect (no callback). Provides transparency about the tool's behavior, though it omits idempotency, permissions, and error handling.

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 concise and includes only essential information. It is well-structured, easy to understand, and free of unnecessary detail.

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 mutation tool, the description provides sufficient information about its purpose and effect. It does not specify return values or errors, but given the absence of an output schema and the simplicity, it is reasonably complete.

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 sole parameter tran_id is not explicitly described beyond its name and length constraint. The description does not clarify that it is the transaction identifier or provide additional context, adding no extra meaning to the schema.

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 the action (Cancel/close) and the resource (transaction), with examples. The phrase 'no callback sent' distinguishes it from other transaction-related 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?

Does not explicitly instruct when to use this tool over alternatives like refund or check_transaction. It mentions the effect but lacks direct guidance on selection criteria.

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