delete_user

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

Annotations already mark destructiveHint=true and readOnlyHint=false. The description adds the behavioral note 'Confirm with the user before calling' and includes a 'DESTRUCTIVE' prefix, providing practical guidance on required user confirmation beyond what annotations convey. It does not mention other side effects, but for a simple delete this is sufficient.

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 redundant, stating 'Delete a user' twice and including an extra line 'Delete an existing user'. The prefix with emoji and method info is extraneous. It could be condensed into a single clear sentence. The redundancy wastes space without adding clarity.

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 simple destructive tool with one parameter and annotations present, the description covers the basic action and a safety requirement. However, it lacks information about return values, authorization requirements, or potential errors, which would improve completeness. The output schema is absent, so the description could provide more context.

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 already describes the only parameter 'id' as 'ID of the user you wish to delete' with 100% coverage. The description does not add any additional parameter context or formatting details, so it meets the baseline without adding extra value.

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 'Delete a user' and 'Delete an existing user', using a specific verb and resource. It unambiguously identifies the action, distinguishing it from other delete tools by resource name, even without explicit sibling differentiation.

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 includes the important guideline 'Confirm with the user before calling', but does not specify when to use this tool versus other delete tools (e.g., delete_contact, delete_account). The context of use is implied by the resource type, but no explicit alternatives or exclusions are provided.

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