wafeq_debit_notes_line_items_destroy

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

Annotations already mark the operation as destructive, and the description adds value by explicitly saying 'Permanently removes the record' and stating exactly what gets destroyed: the debit note line item. This reinforces irreversibility without contradicting the annotations.

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 short and front-loaded, but it repeats the same idea: '🔴 DESTRUCTIVE · deletes', 'Delete debit note line item', and 'Endpoint for deleting an existing debit note line item' all say essentially the same thing. It could be tightened to a single clear sentence plus the permanence warning.

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 three-parameter destructive operation with no output schema, the description covers the resource, endpoint, permanence, and idempotency semantics. It does not mention response behavior, prerequisites, or error conditions, but the annotations carry the destructive safety profile.

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 leaves debit_note_id and id undocumented, but the endpoint path in the description clarifies that debit_note_id is the parent debit note ID and id is the line item ID. The optional idempotency_key is already thoroughly explained in 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 action ('Delete debit note line item') and the exact resource ('Debit Note Line Items'), reinforced by the endpoint path. It is clearly distinguishable from sibling line-item retrieve, update, and partial_update 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 given about when to use this tool versus alternatives, nor are prerequisites or exclusions mentioned. The agent must infer usage from the verb 'delete' and the tool name.

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