users_delete_user

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

No annotations are provided, so the description carries the full behavioral burden, and it discloses almost nothing. It does not state that deletion is permanent/irreversible, what related data (subscriptions, devices, connections) is affected, or what permissions are needed. The confirm-gate behavior is only visible in the schema, not the description.

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?

It is short and front-loaded with the HTTP method and path, with no wasted words. However, the tag line 'Tags: Users Controller' adds no value, and the overall brevity is under-specification rather than earned conciseness.

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, zero-annotation, no-output-schema tool with half its parameters undocumented, the description is far too thin. An agent gets no warning about irreversibility, cascading effects, or required permissions before invoking a delete.

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 only 50%: the confirm parameter is documented in the schema, but userId is not described at all. The description does not compensate by explaining that userId identifies the target user, adding no meaning beyond the path template.

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 states a specific verb and resource ('Delete user') and echoes the route 'DELETE /api/users/{userId}', so an agent knows exactly what it does. It does not, however, distinguish it from siblings like users_bulk_actions_bulk_delete_users or users_disable_user/revoke_user_subscription, so it falls short of a 5.

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?

There is no guidance on when to use this single-user delete versus the bulk delete tools or the softer disable/revoke siblings. The only hint is the route template itself, which is implied rather than explained.

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