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

With no annotations provided, the description carries the full behavioral burden and does so well. It discloses that the original ledger entry is retained and marked reversed, that the invoice balance is recomputed, and that no refund or customer notification occurs—critical details for an agent deciding whether this action is appropriate.

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 three short sentences with no filler. It front-loads the primary purpose, then efficiently adds the most important behavioral caveats. Every sentence contributes useful information.

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 single-parameter mutation with no output schema, the description is complete enough for safe invocation. It covers the action, the ledger effect, the invoice effect, and the important non-effects (no refund, no notification), leaving no critical unknown for an agent choosing or calling the tool.

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 0%, so the description should compensate, but it never mentions paymentId or its format/source. However, the parameter name and the description's phrase 'a payment' make it inferable that paymentId is the identifier of the erroneous payment, so the meaning is minimally adequate.

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 states a specific verb ('Reverse') and resource ('a payment that was recorded in error'), making the tool's purpose immediately clear. It also implies the distinction from siblings like invoice_payments_record and invoices_void by focusing specifically on reversing an erroneous payment rather than recording or voiding.

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 gives a clear usage context: use this when a payment was recorded in error. It does not explicitly name alternative tools or state when not to use it, but the context is specific enough that an agent can reasonably select it over the sibling payment/invoice tools.

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