users_bulk_delete

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the agent knows this is a destructive write operation. The description adds no further behavioral context such as permanence, cascading effects, authorization requirements, or batch semantics beyond the word 'Bulk'.

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, front-loaded sentence with no filler or repetition. Every word contributes to stating the operation and its input.

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 bulk mutation with no output schema, the description is incomplete. It does not warn about irreversible deletion, specify authentication requirements, describe whether failures are partial or atomic, or explain the maximum batch size, all of which an agent needs for safe invocation.

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?

With 0% schema description coverage, the description must compensate for the undocumented userIds parameter. It says 'by User IDs', which clarifies that numeric user IDs are expected, but adds little beyond the schema's property name and omits the array nature, item type, and the min/max limits already present in the schema.

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 ('Bulk delete') and resource ('users') plus a selection mechanism ('by User IDs'), which implicitly distinguishes it from users_delete and users_bulk_delete_by_status. However, it does not name or explicitly contrast with any sibling tool, so it falls short of the top score.

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 no guidance on when to use this tool versus users_delete (single deletion) or users_bulk_delete_by_status (status-based bulk deletion). It also omits any prerequisites, warnings, or context about appropriate scenarios.

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