seerr_delete_user

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

Annotations already declare destructiveHint=true and readOnlyHint=false. The description's 'DESTRUCTIVE: this deletes data' is consistent but adds minimal extra context; it doesn't specify the scope of deletion (e.g., associated requests, watchlists) or irreversibility.

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 to the point, but the awkward phrasing 'by ID DESTRUCTIVE:' lacks punctuation and the warning is somewhat redundant. Still, it is concise and front-loaded.

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?

Given the tool's low complexity (one parameter) and existing annotations/output schema, the description covers the basic action and destruction warning. However, it omits side effects or usage constraints, which is significant for a destructive operation.

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 schema lists user_id with 0% description coverage. The description's 'by ID' clarifies that user_id is the identifier of the user to delete, providing essential meaning beyond the bare integer type. However, it doesn't explain how to obtain the ID or any constraints (e.g., cannot delete yourself).

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 uses the specific verb 'Delete' and identifies the resource 'user by ID', which clearly distinguishes it from sibling tools like seerr_get_user and seerr_update_user. The DESTRUCTIVE warning is additional context but doesn't obscure the purpose.

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 explicit guidance on when to use this tool versus alternatives, nor any exclusions or prerequisites. The DESTRUCTIVE warning implies caution but does not state when this tool should be used (e.g., 'use when removing a user permanently').

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