wafeq_invoices_destroy

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

The description explicitly warns with '🔴 DESTRUCTIVE' and states 'Permanently removes the record,' adding irreversibility context beyond the destructiveHint annotation. It does not disclose side effects such as cascading deletion or authorization requirements, but the annotation already covers the destructive flag, so the added context is meaningful.

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 text repeats the same idea several times: 'DESTRUCTIVE · deletes · Invoices', 'Delete invoice', 'Endpoint for deleting an existing invoice', and 'Permanently removes the record'. It is short, but the redundancy wastes space and the structure is choppy.

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?

The combination of annotations, schema, and description covers the core destructive behavior and the idempotency semantics. However, it leaves gaps such as what the required `id` refers to, whether deletion can be undone, and what response or related records are affected; for a destructive endpoint this is incomplete.

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?

The only parameter documentation comes from the schema's detailed idempotency_key description; `id` is left as a bare string. The description adds nothing about either parameter, so it fails to compensate for the undocumented required invoice 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?

The description states exactly that the tool deletes an invoice, gives the HTTP endpoint, and adds that the record is permanently removed. It clearly identifies the target resource (invoices) and the delete action, so an agent can distinguish it from retrieve/update invoice tools.

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 is provided about when deletion is appropriate, what prerequisites exist, or which alternative to use instead (e.g., update/partial_update rather than destroy). The text only restates the action and endpoint, leaving the agent to infer the usage context.

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