delete_user

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

Annotations already indicate destructiveHint=true, so the description's 'Deletes a user' is consistent. However, the description adds no extra behavioral context (e.g., irreversibility, permission requirements, cascading effects). It meets the minimum bar given the annotation.

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 has two sentences, the first being generic ('Manage users who have access to the DoiT platform.') which adds little value. The second sentence is direct. It could be more concise by removing the first sentence.

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 operation with no output schema, the description is too sparse. It does not mention the outcome (e.g., confirmation, return status), whether the deletion is permanent, or any effects on related data. It lacks completeness for safe usage.

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?

With only 50% schema description coverage, the description does not explain the parameters at all. The 'customerContext' parameter is described in the schema, but the required 'id' parameter lacks any description in both schema and tool description. 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 clearly states that the tool deletes a user, which aligns with the tool name 'delete_user'. It distinguishes from sibling user tools like invite_user, update_user, and validate_user by explicitly using 'Deletes a user'.

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, such as when a user should be removed versus disabled, or any prerequisites like ownership of the user. It only states the action without context.

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