npm_delete_user

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

No annotations are supplied, so the description carries the full disclosure burden and delivers almost none of it: it does not say whether deletion is permanent/irreversible, whether it cascades (e.g., access lists, permissions), whether elevated permissions are required, or whether the user must be disabled first. 'Delete' is the only behavioral signal given.

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?

A single four-word sentence with the destructive action front-loaded and zero filler. Nothing could be removed without losing meaning.

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 destructive mutation with no annotations and no output schema, the description is too thin: an agent cannot tell whether the operation is reversible, what permissions it needs, or what happens to dependent resources. The schema covers the input exhaustively, but the behavioral context a deletion tool demands is absent.

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?

Schema description coverage is 100% and the single user_id parameter is fully documented in the schema, so the schema does the heavy lifting. The description adds only 'by ID', which mirrors the schema rather than extending it, making the baseline of 3 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 states a specific verb and resource ('Delete a user'), which separates it from other delete siblings such as npm_delete_dead_host or npm_delete_certificate. It does not, however, distinguish itself from npm_delete_user-adjacent lifecycle tools or mention the inverse npm_create_user, so it sits just below the top band.

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 statement of when to use this tool versus alternatives, no prerequisites, and no note that the user must exist or be fetched via npm_get_user/npm_list_users first. The agent is left to infer usage entirely from the name.

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