deleteUser

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

Discloses destructive nature, irreversibility, no soft-delete via API, and need for intent confirmation. Aligns with annotations without contradicting them.

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?

Description is detailed but each sentence adds value. Front-loaded with purpose and guidelines. Could be slightly trimmed but overall well-structured.

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?

Covers return values, parameter interactions, and alternatives. Given no output schema, it provides enough context for an agent to use 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?

Adds meaning to both parameters: user_id as required, delete_images as optional with explanation of its effect. Schema had 50% coverage (delete_images described), so description compensates and adds 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?

Clearly states the tool permanently deletes a user by ID. Distinguishes from siblings like updateUser for reversible removal, and from other delete tools by specifying it's for user records.

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?

Explicitly lists when to use (GDPR, cleanup, duplicates) and when not to (prefer updateUser with active=3 for reversible removal). Also mentions optional image deletion and provides alternative tool name.

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