wafeq_invoices_line_items_destroy

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

The description explicitly warns '🔴 DESTRUCTIVE' and states that the record is 'Permanently removed,' which adds meaningful behavioral context beyond the destructiveHint annotation. This makes the irreversibility of the operation clear, even though auth, rate limits, and side effects are not mentioned.

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 destructive warning and endpoint path are front-loaded, which helps an agent quickly recognize the nature of the operation. But 'Delete invoice line item' and 'Endpoint for deleting an existing invoice line item' are near-duplicates, making the description slightly padded.

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 destructive endpoint with only two required parameters, the description gives enough resource and path context to understand what will be deleted, and the annotations cover safety and idempotency. What is missing is usage guidance and any note about downstream effects, such as whether deleting a line item recalculates invoice totals.

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 endpoint path clarifies that invoice_id identifies the parent invoice and id identifies the line item, which is useful because the schema gives only bare string types for these required parameters. However, the description does not add much beyond that path context, and the idempotency_key parameter is already well-covered by the schema description.

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 uses a specific verb ('delete') and identifies the exact resource ('Invoice Line Items'), reinforced by the DELETE endpoint path. It is clear and unambiguous, though it does not explicitly differentiate itself from sibling line-item destroy tools and largely restates the tool title.

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?

There is no guidance on when to use this tool over alternatives such as update, partial_update, or other line-item destroy endpoints. Saying it is an 'Endpoint for deleting an existing invoice line item' restates the operation rather than providing decision criteria, preconditions, or exclusions.

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