seerr_delete_request

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

The description repeats the destructiveHint annotation by saying 'DESTRUCTIVE: this deletes data,' adding no new behavioral context beyond what is already structured. It does not mention irreversibility, cascading effects, or permission requirements.

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 extremely short and front-loaded, but the phrase 'DESTRUCTIVE: this deletes data' is redundant given the annotation and the verb 'delete' already convey this meaning. It wastes the little space it uses.

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, the description plus annotations are minimally sufficient. However, it lacks context about the request_id source, prerequisites, or any side effects, leaving the agent to infer these details from the schema and tool name.

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 description provides no explanation of the request_id parameter. With schema description coverage at 0%, the agent receives no guidance on how to find or format the request_id, making this a significant gap.

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 clearly states the action (Delete) and resource (request), which distinguishes it from sibling tools like list_request or create_request. However, it is essentially a restatement of the tool's name and does not specify that it deletes a single request by ID.

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 guidance is provided on when to use this tool versus alternatives, or any prerequisites or exclusions. The description is purely declarative and does not help the agent decide when to invoke this deletion operation.

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