delete_payment

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

With no annotations, the description carries the full behavioral burden and delivers almost nothing: it does not say whether the delete is hard or soft, reversible, what permissions or entity state are required, or what happens to linked invoices/deposits. Only the bare implication of a destructive mutation is conveyed, and that comes from the tool name itself.

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?

One front-loaded sentence with no wasted words, which is good structure, but the brevity here reflects under-specification rather than economy — nothing about mutation risk or the ambiguous parameter is covered.

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?

A destructive mutation tool with zero annotations, no output schema, and an undocumented nested parameter requires far more than a single sentence. An agent has no way to safely construct the call or predict failure modes from this definition.

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 description coverage is 0% for the single required parameter, which is an untyped nested object named 'idOrEntity' with additionalProperties allowed. The description adds nothing about whether this accepts an ID string, a full entity payload, or a sync token, leaving the caller to guess at the most consequential input.

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 verb+resource pair ('Delete a payment') is specific and, combined with the QuickBooks Online context, an agent can distinguish it from create_payment, update_payment and get_payment. It does not differentiate from adjacent delete siblings such as delete_bill_payment, delete_refund_receipt, or delete_sales_receipt, which matters in a toolset this large.

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?

No guidance on when to use this versus delete_bill_payment or delete_refund_receipt, no prerequisites (e.g. whether the payment must be unapplied or unlinked first), and no statement about when deletion is inappropriate versus voiding.

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