delete_user

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

Annotations already declare destructiveHint: true. The description adds specific behavioral details: 'cannot be undone' and 'the user loses access immediately', which provide valuable context beyond the annotation. No contradiction with annotations.

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 sentence that efficiently conveys the essential information. It front-loads the action and includes key caveats (permanence, immediate effect) with no wasted words.

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 tool's simplicity (single required parameter, no output schema), the description is fully adequate. It explains the input, the irreversible nature, and the immediate consequence, covering all needed context for an AI agent to use the tool correctly.

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 schema includes a single required parameter 'idOrEmail' with description 'User ID or email', and coverage is 100%. The description simply mirrors this ('by ID or email') without adding additional semantic meaning or formatting details, so it meets the baseline expectation.

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 ('Permanently remove a user') and the resource ('from the instance'), along with the identification method ('by ID or email'). It distinguishes this tool from sibling tools like 'deactivate_workflow' or 'remove_user_from_project' by emphasizing permanence and immediate loss of access.

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 clear context that this tool is for permanent removal and cannot be undone, which implies when to use it. However, it does not explicitly state when not to use it or mention alternatives (e.g., deactivating a user or changing roles), which would be helpful for an AI agent.

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