delete_user

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

The description adds the ADMIN requirement, which is useful behavioral context beyond the destructiveHint annotation. However, it does not disclose consequences like permanence, cascading effects, or whether the user's data is affected. The destructiveHint annotation already covers the destructive nature, so the description adds limited but meaningful context.

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 concise, using two short sentences. Every word contributes: it states the action and the required permission. No filler or redundancy.

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 delete operation with one parameter and a destructiveHint annotation, the description covers the core purpose and the critical ADMIN requirement. An output schema is present, and the tool's complexity is low, so the description is sufficiently complete, though it could mention permanence.

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 does not elaborate on the meaning or format of 'user_id'. With 0% schema description coverage, the description is expected to compensate, but it only mentions 'user' without explaining how to identify the target user. The agent must infer the parameter's semantics from the tool name.

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' with resource 'user', clearly distinguishing it from sibling tools like create_user and update_user. It is not a tautology and leaves no ambiguity about the operation.

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 only mentions 'Requires ADMIN' as a prerequisite, but provides no guidance on when to use this tool versus alternatives such as update_user or delete_api_key. It does not state any conditions under which deletion is appropriate or suggest using a non-destructive alternative.

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