void_transaction

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

No annotations provided, so the description carries full burden. It discloses key behavioral traits: preserves for audit purposes, zeroes out all split values (a significant side effect not obvious from the name). However, it does not mention whether this is reversible (there is an unvoid_transaction sibling suggesting reversibility, but the description doesn't state it explicitly), nor what happens to reconciled/linked splits.

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?

Four tight paragraphs, zero filler. The key contrast (safe void vs delete) is front-loaded. Every sentence earns its place, and the Args section is a clean, minimal parameter restatement. No redundancy with the input schema.

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?

There is an output schema (context signal), so return values need no explanation. The tool has a serious side effect (zeroing all splits), which is disclosed. The only gap: it doesn't note that unvoid_transaction is the reversal operation, but that sibling's own description likely covers it. Adequate for the complexity level.

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 covers only 50% of params in description (guid has description, reason has none). The description compensates by explaining the guid format beyond schema (32-char hex or 8+ char prefix, which schema also documents) and adding the crucial reason requirement: 'required for audit trail'. This adds meaning the schema lacks for the reason parameter.

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 verb+resource ('Void a transaction') and explicitly contrasts with delete ('proper accounting void, not delete'). It distinguishes from sibling delete_transaction and pairs with unvoid_transaction. The distinction between void (preserves record, zeroes splits) vs delete is precisely what the agent needs.

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 states 'Use this instead of delete when you need to maintain an audit trail', giving a clear when-to-use condition and naming the alternative (delete). This directly guides selection among sibling tools delete_transaction, unvoid_transaction, and update_transaction.

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