wafeq_debit_notes_destroy

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

Annotations already provide destructiveHint=true, readOnlyHint=false, and idempotentHint=true, so the bar is lower. The description adds value beyond those flags by stating 'Permanently removes the record,' which clarifies this is a hard delete rather than a soft delete or reversible action. The idempotency_key schema description further explains retry-safe behavior, which aligns with idempotentHint=true.

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 front-loaded banner line ('🔴 DESTRUCTIVE · deletes · Debit Notes · DELETE /debit-notes/{id}/') is an efficient, attention-grabbing summary. However, 'Delete debit note' and 'Endpoint for deleting an existing debit note' are near-duplicate restatements of the same idea, and the only unique behavioral detail (permanence) is buried at the end. Two of the four sentences are redundant.

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 2-parameter, 1-required-parameter delete with no output schema, the combination of annotations, description, and schema covers what an agent needs: destructive and permanent nature, idempotency behavior, the endpoint, and the required id. It would be more complete with notes on failure preconditions (e.g., whether posted or linked debit notes can be deleted) or cascading effects on line items, but nothing essential to invoking the tool is missing.

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 50%. The idempotency_key parameter is richly documented in the schema (header mapping, auto-generated UUID v4, retry-safety semantics), but the required 'id' parameter has no description in either the schema or the tool description. The id's meaning is self-evident from context, so the description need not elaborate, but it adds zero param-level value beyond the schema.

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 a specific verb ('deletes'), the resource ('Debit Notes'), the exact endpoint ('DELETE /debit-notes/{id}/'), and the consequence ('Permanently removes the record'). This is unambiguous and clearly distinguishes the tool from siblings like wafeq_debit_notes_list, wafeq_debit_notes_update, and wafeq_debit_notes_partial_update.

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?

Usage is implied rather than explicit: the destructive banner and 'deletes' make it clear this is the tool for removing a debit note, and 'Permanently removes' warns against casual use. However, the description never names alternatives or states when not to use it (e.g., 'use update for reversible changes'), leaving the agent to infer the selection logic.

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