paymenter_delete_invoice

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

With no annotations provided, the description carries the full behavioral burden. It does disclose the one trait that matters most for a delete tool, irreversibility ('Permanently'), but is silent on permission requirements, cascade effects on related records, and what happens if the invoice is not found.

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?

A single four-word sentence that front-loads the permanence qualifier and contains no filler. Nothing could be removed without losing meaning.

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 destructive tool with a fully documented schema, the description covers the essential behavior (permanent removal). The remaining gap is the absence of annotations or text describing side effects, failure modes, and permission needs on a destructive operation.

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 100%, with 'invoice_id' documented as 'Invoice ID to delete', so the parameter is fully explained by structured data. The description adds nothing beyond that, which is the expected baseline when the schema does the heavy lifting.

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?

States a specific verb and resource (delete an invoice record) and adds the crucial qualifier 'Permanently', so the agent immediately knows the operation is destructive. It does not explicitly name or contrast with sibling delete tools (paymenter_delete_order, paymenter_delete_user), but the resource noun 'invoice' makes the scope unambiguous.

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?

There is no when-to-use guidance, no prerequisites, and no mention of alternatives such as paymenter_update_invoice or paymenter_cancel_service for cases where deletion is not appropriate. The word 'Permanently' hints that care is needed but offers no routing or caution instructions.

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