token_bowl_chat_admin_delete_user

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

With no annotations, the description carries the full burden and does well: it declares the operation irreversible, permanent, admin-only, and names the failure modes (NotFoundError, AuthenticationError). It omits what happens to the user's associated data/messages and the response shape, but the safety-critical traits are disclosed.

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 lead sentence is front-loaded with the admin constraint and irreversible warning before the docstring-style Args/Raises blocks. Minor redundancy between 'Permanently delete a user account' and 'remove a user account completely,' but no meaningful waste.

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, annotation-less mutation with no output schema, the description covers the irreversible nature, the privilege requirement, and expected errors. Cascade effects on related data are the only notable gap.

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?

Schema description coverage is 0%, so the description must compensate, and it does identify the single parameter as 'the username of the account to delete.' That is marginally more than the schema title, but stops short of format/validation guidance, so it is only adequate.

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?

States a specific verb (delete) and resource (user account) with the [ADMIN ONLY] scope front-loaded. It is clearly distinguishable from siblings like token_bowl_chat_admin_update_user and token_bowl_chat_admin_get_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 gives the scenario ('Use this to remove a user account completely') but never names alternatives or exclusions, e.g. when to use admin_update_user instead or how it differs from admin_delete_message. Usage is implied rather than routed.

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