deleteUser

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

Annotations only state readOnlyHint: false, which already indicates mutation. The description adds nothing beyond that—it does not disclose side effects, irreversibility, or permission requirements. For a destructive operation, the description should offer more context, but it stays at the bare minimum.

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?

While 'Delete user' is extremely brief with no redundancy, it is under-specified to the point of being unhelpful. The description is too sparse to earn its place; it provides no practical value beyond the name.

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 nested parameter object, no output schema, and minimal annotations, the description is grossly incomplete. It does not explain the parameters, the response, the impact of deletion, or any error conditions. An agent would struggle to use this tool correctly with only this description.

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 0%, and the description does not mention the pathParams, format, or userId parameters. The agent cannot infer what format or userId mean or what values are valid beyond the schema's enum and type. The description completely fails to compensate for the schema's lack of descriptions.

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 states the action (delete) and the resource (user). It is specific enough to distinguish from other user-related tools like getUser or updateUser, and no sibling tool duplicates the delete-user function.

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 this tool versus alternatives. It does not mention permanence, prerequisites, or situations where deletion might be inappropriate. The agent is given no context to decide if this is the right call.

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