void_transaction

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

Annotations already indicate destructiveHint=true and idempotentHint=true. The description adds valuable behavioral context: voiding preserves the transaction but zeroes split values, and a reason is required for audit purposes. It does not fully explain whether voiding is reversible, though the sibling unvoid_transaction hints at it.

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 tight and front-loaded: purpose, behavior, usage guidance, then parameters. Every sentence contributes meaningful information, and the Args block is 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?

Given the tool's moderate complexity, the presence of an output schema, and annotations covering destructiveness and idempotency, the description provides what an agent needs: what the tool does, when to use it, and what side effects to expect. No critical gap is apparent.

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 only 50%, with 'reason' lacking a description. The description compensates by explaining that reason is required for the audit trail, giving it clear semantic purpose. The guid parameter's description matches the schema but adds nothing new, though this is not a significant shortcoming.

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 opens with the specific verb 'Void a transaction' and immediately clarifies the accounting-specific behavior ('proper accounting void, not delete'). It also names the key distinction from delete_transaction, making the tool's purpose unmistakable.

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 explicitly says 'Use this instead of delete when you need to maintain an audit trail.' This directly tells the agent when to choose this tool over the sibling delete_transaction and gives a clear selection condition.

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