void_transaction

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only says 'void a pending transaction' but does not explain the state change, whether the void is reversible, what happens if the transaction is not pending, or any side effects. This is minimal for a mutation operation.

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 a single clear sentence with no filler. It is front-loaded and succinct, but it is also extremely brief, bordering on under-specification. It earns a 4 for being direct and concise, though it could have included more useful context in a second sentence.

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?

The tool has one parameter and no output schema, but it is a mutation operation that likely has side effects. The description is too sparse to be contextually complete: it does not mention the difference from refund, the pending-transaction restriction's practical use, or what the response might indicate. More context is needed for an AI agent to use this safely.

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 input schema has 100% parameter description coverage for 'tran_ref' ('Transaction reference to void'), so the schema already explains the parameter. The description adds no additional parameter semantics, and the baseline of 3 is appropriate given the schema already handles it.

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 ('void') and the resource ('a pending transaction'), so the core purpose is understandable. However, it does not distinguish this tool from sibling 'refund_transaction', which is also a transaction reversal but with a different meaning (refund after capture vs void before capture).

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 no guidance on when to use this tool versus alternatives. There is no mention of when a void is appropriate (e.g., only for pending/unsettled transactions) or when to prefer refund_transaction instead. Sibling tool names are available but no explicit comparison is made.

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