Delete user

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

While annotations indicate destructiveHint=true, the description adds 'Requires confirmation' but the input schema does not require the confirm parameter, creating a mismatch. It discloses that the username must match the target id, but does not explain what happens if they don't match or if the user exists. This is insufficient beyond annotations.

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?

Two concise sentences with no superfluous words. The first sentence states the action, the second adds essential conditions. Ideal length.

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 tool with no output schema, the description covers the basic action and key constraints. However, it lacks guidance on return values, error handling, or side effects, which are important for an agent performing a permanent deletion.

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?

With schema description coverage at 0%, the description provides some meaning: 'username must match the target id' adds a constraint, and 'Requires confirmation' hints at the confirm parameter's role. However, it does not explain the 'id' parameter or detail the confirmation mechanism, leaving gaps.

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 'Permanently delete a user,' which is a specific verb and resource. It adds that confirmation and username matching are required, distinguishing it from other tools, though no explicit distinction from sibling tools is made.

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 usage conditions (confirmation, username matching target id) but does not provide explicit guidance on when to use this tool versus alternatives like disabling a user or when not to use it. No alternatives are mentioned.

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