delete_user

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

With no annotations, the description must fully disclose behavior. It labels the operation as destructive and admin-only, but it fails to mention whether deletion is permanent, what cascading effects occur (e.g., deleting associated records), whether the action is reversible, or if there are any authorization checks beyond 'system-level.' This is insufficient for a high-risk operation.

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 consists of only two short sentences, each adding distinct value: the action and the required privilege level. No redundant phrases or excessive detail. It is optimally front-loaded and efficient.

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 simple input (1 required parameter, no output schema) and high schema coverage, the description is minimally adequate. However, because it is a destructive admin operation, missing details about return values, error handling, or consequences beyond deletion make it somewhat incomplete for a cautious agent.

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 provides 100% coverage for the single parameter 'user_id' with the description 'User ID to delete.' The tool description repeats 'by user ID' but adds no new semantic meaning. At full schema coverage, a baseline of 3 is appropriate as the description does not enhance understanding of the parameter.

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 it deletes a user by user ID and adds that it is a system-level administrative operation. This distinguishes it effectively from sibling tools like get_user, create_user, or search_users, which serve different purposes.

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 implies through 'system-level administrative operation' that elevated privileges are required, but it does not explicitly state prerequisites, when to use versus alternatives, or when not to use this tool (e.g., soft-delete options, user must exist). No guidance on side effects or recovery is provided.

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