users_delete_user

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

With no annotations provided, the description must carry the full burden of behavioral disclosure. It does clearly state that deletion is permanent, which is critical. However, it does not mention permissions, cascade effects, or other consequences beyond the account removal, so it only partially covers behavior.

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 five-word sentence, 'Permanently delete a user account,' that front-loads the action and object with no redundant or extraneous content. It is highly concise and 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?

For a tool with one required parameter and no output schema, the description covers the core action and permanence. It might optionally mention admin permissions or related data effects, but those are not essential for basic selection and invocation. The description is complete enough for this simple delete tool.

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 provides 100% coverage for the single parameter user_id with the description 'User to delete.' The tool description adds no additional semantic detail about the parameter, so baseline 3 is appropriate given the schema's completeness.

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 'Permanently delete a user account' uses a specific verb (delete) and resource (user account), clearly stating what the tool does. It distinguishes from sibling tools like users_reset_user_password or users_set_user_role by making the destructive action explicit.

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 does not explicitly state when to use this tool or mention alternatives, but the verb 'delete' implies usage for removing users, and 'permanently' indicates irreversibility. Usage guidance is present only implicitly, not as direct guidance.

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