delete-user

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

The description only states the basic action. Annotations indicate readOnlyHint=false (destructive) and openWorldHint=true (possible side effects), but the description does not add any behavioral context, such as cascading deletions or error responses. The agent is left uninformed about what happens beyond the deletion itself.

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 concise at three words, but this brevity comes at the cost of missing critical information. It is appropriately front-loaded but does not earn its place by providing sufficient insight.

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 single parameter and no output schema, the description fails to explain return behavior, error handling, or side effects. For a destructive operation with an open-world hint, more context is needed for safe invocation.

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 sole parameter 'name' has no description in the schema (0% coverage). The description does not explain what 'name' refers to (e.g., username, ID, full name), leaving the agent to guess. No format or constraints are provided.

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' clearly states the verb and resource, distinguishing it from other delete tools that target different resources (e.g., queues, exchanges). However, it does not differentiate from the sibling 'bulk-delete-users' in terms of scope or method.

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 provided on when to use 'delete-user' versus alternatives like 'bulk-delete-users', nor any prerequisites or context such as the user needing to exist or having permissions. The agent receives no decision-making support.

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