wafeq_simplified_invoices_destroy

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

Annotations already declare destructiveHint=true and readOnlyHint=false, and the description is consistent with both. It adds value beyond the annotations with 'Permanently removes the record,' which tells the agent the deletion is irreversible (not a soft delete) — a behavioral fact the annotations do not convey.

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 structured first line effectively front-loads the destructive warning, but the prose is redundant: 'Delete simplified invoice' and 'Endpoint for deleting an existing simplified invoice' restate the same fact, leaving only 'Permanently removes the record' as unique content. Three of the four lines could be collapsed into one.

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?

Adequate for a simple 2-parameter delete: it identifies the target resource, the endpoint, and permanence, while the annotations cover the safety and idempotency profile. It is silent on cascading effects (e.g., what happens to the invoice's line items) and on any preconditions or status restrictions for deletion, which matter for 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 exactly 50%. The idempotency_key parameter is already richly documented in the schema (header name, auto-generated UUID, retry safety), so the description adds nothing there. For the undocumented id parameter, the description offers only marginal help by showing it as the path variable in 'DELETE /simplified-invoices/{id}/'.

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 ('deletes', 'removes') and a specific resource ('simplified invoice'), and repeats it consistently across the label and prose. The resource scope also distinguishes it from sibling wafeq_invoices_destroy, which targets regular invoices.

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 when-to-use or when-not-to-use guidance is provided. The description never explains when this destroy tool should be selected over wafeq_simplified_invoices_update/partial_update, nor does it warn that deletion is irreversible as a usage caution — the 'DESTRUCTIVE' label and 'Permanently removes' read as behavior warnings, not selection criteria.

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