users_delete_user

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

The description is consistent with the annotations (destructiveHint: true), but it does not add any behavioral context beyond what the annotations already declare. Since the annotations indicate destructive behavior, the description does not need to repeat it, but it also fails to disclose any additional traits such as irreversibility or cascading effects. The bare statement 'Delete User' provides no extra insight.

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 short, essentially just restating the tool name. While it contains no fluff, it is under-specified and lacks any structured detail. It is concise but not effectively structured for an agent to understand the operation's implications.

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 delete operation, the description is insufficiently complete. It does not mention whether the deletion is permanent, if there are any safeguards, or what the consequences are. Although the output schema is absent and complexity is low, the lack of contextual warnings or side effects leaves the agent without critical information when deciding to invoke the tool.

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 input schema fully describes the single parameter 'userId' as a path parameter, and the description does not add meaningful information about it. With 100% schema coverage, the baseline is 3, and the description offers no further explanation of the parameter's format, requirements, or usage.

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 User' clearly states a specific verb (delete) and resource (user), which is distinguishable from sibling tools like users_get_user and users_update_user. It is concise and unambiguous, though it lacks any additional nuance about the scope or permanence of the deletion.

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 provides no guidance on when to use this tool versus alternatives. There is no mention of context, prerequisites, or exclusions. For instance, it does not clarify whether this should be used only when a user is no longer needed, or if there are any safety considerations before deleting. The agent is left to infer usage from the name alone.

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