wafeq_revenue_recognitions_destroy

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

Annotations already declare destructiveHint=true, and the description adds value by explicitly warning '🔴 DESTRUCTIVE' and stating 'Permanently removes the record,' which communicates irreversibility. This does not contradict any annotation.

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 front-loaded with the destructive warning and endpoint, but it is redundant: '🔴 DESTRUCTIVE · deletes', 'Delete revenue recognition', and 'Endpoint for deleting an existing revenue recognition' all convey nearly the same information. It is compact yet repetitive.

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 destructive tool with one required parameter, the description, schema, and annotations together are sufficient: the resource is identified, idempotency is documented in the schema, and permanence is stated. No output schema is present, but a delete operation's return value is not essential 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?

The required 'id' parameter has no schema description, but the endpoint path '/revenue-recognitions/{id}/' and the phrase 'existing revenue recognition' imply it is the resource identifier. The 'idempotency_key' parameter is already fully described in the schema, so the description does not need to repeat it.

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 is explicit: it begins with '🔴 DESTRUCTIVE · deletes · Revenue Recognitions · DELETE /revenue-recognitions/{id}/' and further states 'Delete revenue recognition' and 'Permanently removes the record.' The verb, resource, endpoint, and hard-delete semantics are all clear, making it easy to distinguish from retrieve/update siblings.

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?

'Endpoint for deleting an existing revenue recognition' implies the tool is meant for deleting a record that already exists, but it does not name alternatives, exclusion conditions, or when not to use it. Usage is implied rather than explicitly guided.

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