users_delete

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

With no annotations available, the description must carry the full behavioral disclosure burden. 'Delete a user account' implies a destructive action but does not mention irreversibility, cascading effects on user data, or required permissions. The agent is left without critical cautionary context.

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 a single short sentence with no wasted words, and it is front-loaded with the main verb. However, it is so terse that it provides little beyond the tool name, slightly limiting its overall effectiveness despite being concise.

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 tool with no annotations and no output schema, this description is under-specified. It omits permanent effects, potential impacts on related resources, authorization needs, and any guidance about when deletion is appropriate versus suspension. The context is insufficient for an agent to safely invoke this 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 has 100% description coverage for the single parameter 'id' ('User ID to delete'). The tool description adds no additional parameter semantics beyond that schema, so the baseline score of 3 applies.

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 specifies a verb ('Delete') and resource ('user account'), which is unambiguous. However, it does not explicitly distinguish itself from sibling tools such as users_suspend or users_activate that also act on user accounts, so it falls short of a 5.

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 guidance about when to use this tool as opposed to alternatives like users_suspend or users_activate. The description gives no context about prerequisites, appropriateness, or consequences, so the agent receives no usage direction.

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