wafeq_credit_notes_destroy

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

The annotations already declare destructiveHint=true, but the description adds explicit behavioral context by stating the operation 'Permanently removes the record' and labeling it with 🔴 DESTRUCTIVE. This makes the irreversibility clear beyond a generic 'delete'. No information in the description contradicts the annotations; the idempotentHint is consistent with the schema's idempotency_key explanation.

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 redundant: '🔴 DESTRUCTIVE · deletes · Credit Notes', 'Delete credit note', and 'Endpoint for deleting an existing credit note' all express nearly the same information. The core safety message is front-loaded, but repeated restatements waste tokens and add no new meaning, so the structure does not earn its length.

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 simple delete operation, the description plus annotations cover the essential facts: it is destructive, permanent, and targets an existing credit note by id. However, it omits any mention of the response/return behavior (e.g., 204 or deleted object), possible 404 conditions, or downstream effects on linked records. These gaps are not fatal for invocation but leave the agent with incomplete expectations.

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 schema documents idempotency_key thoroughly but leaves `id` with only a type string. The description partially compensates by showing `/credit-notes/{id}/`, which implies `id` is the credit note identifier, but it never explicitly describes the `id` parameter or its required value. With 50% schema coverage, this is adequate but not strong.

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 names a specific verb ('delete'), a specific resource ('credit note'), and the exact endpoint (DELETE /credit-notes/{id}/), so an agent can clearly identify what this tool does and distinguish it from credit note create/retrieve/update tools. The phrase 'Permanently removes the record' sharpens the intent and distinguishes it from soft-delete or draft-state operations.

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 given for when to choose this tool over alternatives, such as wafeq_credit_notes_update, wafeq_credit_notes_partial_update, or the list/retrieve operations. The description merely restates the purpose ('Endpoint for deleting an existing credit note') without explaining when destruction is appropriate, what prerequisites exist, or when a non-destructive alternative should be used.

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