wafeq_payslips_destroy

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

Annotations already carry destructiveHint=true and readOnlyHint=false, and the description adds value on top by flagging '🔴 DESTRUCTIVE' and emphasizing 'Permanently removes the record,' which communicates irreversibility beyond the structured hint. The idempotency_key schema text also transparently covers retry-safety behavior. 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 front-loaded '🔴 DESTRUCTIVE · deletes · Payslips' marker and endpoint are effective, but the description then repeats the same idea three times: 'Delete payslip,' 'Endpoint for deleting an existing payslip,' and the header line. Only 'Permanently removes the record' carries new information after the first line.

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 an irreversible destructive operation with no output schema, the description omits expected response behavior (e.g., 204 vs. deleted object), consequences for related data (relevant given openWorldHint=true and the existence of payslip pay-items siblings), and safe id-acquisition guidance. The core facts are present, but consequential details that an agent needs before invoking an irreversible delete are 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?

Schema coverage is 50%: idempotency_key is richly documented in the schema, but the required id parameter has no description. The description's endpoint path 'DELETE /payslips/{id}/' obliquely clarifies that id is the payslip identifier, but it adds no format, source, or example for id and nothing further about idempotency_key beyond 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 verb ('deleting') and resource ('payslip') and reinforces it with the endpoint path 'DELETE /payslips/{id}/' and 'Permanently removes the record.' This clearly distinguishes the destroy action from the create/retrieve/update/partial_update payslip siblings, though it never explicitly names a sibling to differentiate from.

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 when-to-use guidance, no mention of prerequisites (e.g., fetching the record first to confirm its id), and no explicit routing away from alternatives. 'Permanently removes the record' serves as a caution, but the description leaves the agent to infer all usage context from the tool name, which is already self-evident.

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