delete_user

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

The description discloses that deletion is permanent and requires admin privileges, but it does not cover other behavioral aspects such as reversibility, cascading effects on associated data, or error conditions. With no annotations, the description carries the full burden, and while it addresses key points, it lacks depth.

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, consisting of two short sentences that immediately convey the tool's purpose and a critical requirement. Every sentence adds value with no extraneous information.

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 tool with one parameter and no output schema, the description provides the essential information: deletion is permanent and requires admin privileges. However, it does not elaborate on implications like data loss or irreversible effects, which would be helpful for an agent to fully understand the impact.

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 only parameter 'id' is described in the input schema as 'Numeric user ID to delete'. The tool description does not add any additional meaning beyond what the schema already provides, so it adds no extra value. With 100% schema coverage, a baseline of 3 is appropriate.

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 that the tool deletes a user permanently, which directly matches the tool name and distinguishes it from other deletion tools. It also specifies a key requirement (admin privileges).

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 mentions that admin privileges are required, which provides some usage guidance, but it does not offer explicit when-to-use or when-not-to-use instructions, nor does it compare to alternative actions like deactivation or other deletion tools.

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