Delete user

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

The annotations already declare destructiveHint=true, readOnlyHint=false, and idempotentHint=true, so the safety profile is largely covered. The description adds useful authorization context with 'Perm: manage_users', but it does not explain irreversibility, side effects on related records, or the confirm/dry_run execution flow.

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 short and front-loaded, but the first two sentences are redundant ('Delete user. Deletes an existing user.'), so not every sentence earns its place. The permission note is useful but appended without further structure.

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?

The tool has a full input schema and an output schema, and annotations cover the destructive/read-only/idempotent traits, which reduces the description's burden. Still, for a destructive user-deletion operation, the description omits irreversibility warnings and the practical confirm/dry_run workflow an agent should follow.

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 100%, and the schema already explains user_id, confirm, and dry_run in detail. The description adds no parameter-specific meaning beyond what the schema provides, so the baseline score of 3 is appropriate.

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 the verb and resource ('Delete user'), so the basic purpose is clear. However, the first two sentences are largely tautological restatements of the tool name and title, and the description does not clarify scope or distinguish this deletion from sibling delete tools such as action1_delete_endpoint or action1_delete_group.

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 tool versus alternatives, no prerequisites beyond the permission string, and no warning about when not to use it. The agent must infer usage entirely from the name and schema.

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