Delete user

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

With no annotations, the description carries full burden for behavioral disclosure. It only states the action (delete) but fails to mention whether deletion is irreversible, cascading, or requires special permissions, leaving critical behavioral traits undocumented.

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 brief (three words) but fails to earn its place because it merely repeats the title. It could be more informative without adding length, making it under-specified rather than concisely effective.

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 absence of annotations and output schema, the description provides almost no context about return values, side effects, or usage constraints. Even for a simple tool, this is insufficient for an agent to understand the full 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 single parameter 'id' has no description in the schema (0% coverage), and the tool description does not explain its meaning or format. While the integer and exclusiveMinimum hint at a user identifier, the description adds no value beyond the schema.

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 'Delete a user.' is a tautology that restates the tool name and title without adding any specificity or distinguishing it from siblings like npm_update_user or npm_set_user_permissions. While the purpose is clear, it does not provide additional context.

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?

No guidance is given on when to use this tool versus alternatives. For instance, it does not clarify prerequisites or that this is the only way to remove a user, nor does it mention related tools like npm_disable_proxy_host for other resources.

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