wafeq_payment_requests_destroy

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

Annotations already mark the operation as destructive and non-read-only, but the description adds the important behavioral detail that the record is permanently removed, reinforcing irreversibility. It also clearly identifies the target resource. No contradiction with annotations was found.

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 key information is front-loaded with the DESTRUCTIVE label and endpoint, but the description is repetitive: 'Delete payment request', 'Endpoint for deleting an existing payment request', and 'Permanently removes the record' overlap. It could be tightened to two clear sentences without losing meaning.

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 operation with strong annotations, the description covers the essential facts: target resource, HTTP endpoint, permanence, and the required id through the schema. The idempotency behavior is handled by the schema's idempotency_key description and the idempotentHint annotation. No output schema exists, but a delete confirmation response is not critical for invocation.

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 coverage is only 50%: the required 'id' parameter has no schema description. The description partially compensates through the endpoint path showing '{id}' and the phrase 'existing payment request', which implies id refers to the payment request to delete. The idempotency_key parameter is fully explained in the schema, so no additional description is needed there.

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'), a specific resource ('Payment Requests'), and the exact HTTP endpoint ('DELETE /payment_requests/{id}/'). This clearly distinguishes it from sibling actions like retrieve, update, or partial_update on the same resource.

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?

The description explains what the tool does but provides no guidance on when to choose it over alternatives, nor any exclusions or prerequisites. It never explicitly says 'use this when you need to permanently remove a payment request' or points to retrieve/update as safer alternatives for non-destructive needs.

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