wafeq_credit_notes_line_items_destroy

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

Annotations already provide destructiveHint and readOnlyHint, and the description adds the important consequence 'Permanently removes the record.' It does not restate idempotency or auth, but the annotations and schema cover idempotency_key behavior.

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 repeats the same core statement three times: 'deletes Credit Note Line Items', 'Delete credit note line item', and 'Endpoint for deleting an existing credit note line item.' Only the permanence statement and endpoint add real value.

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, the endpoint, permanence warning, and idempotency_key schema are sufficient. No output schema exists, so return-value documentation is not required, and nothing critical appears 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?

Only idempotency_key has a schema description, so coverage is low. The endpoint path in the description helps map credit_note_id and id to their roles, but id is still generic and no additional parameter details are provided beyond the path template.

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?

Description names the action 'deletes' and the exact resource 'Credit Note Line Items', and includes the full DELETE endpoint. This clearly differentiates it from sibling destroy tools like wafeq_invoices_line_items_destroy or wafeq_bills_line_items_destroy.

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 explicit guidance on when to use this tool versus alternatives, no prerequisites, and no exclusion criteria. The intended use is only inferable from the resource name rather than stated.

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