users_bulk_delete

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

With no annotations, the description carries the full burden of behavioral disclosure. It conveys only the core destructive action and adds no information about permanence, cascading effects, permissions, or whether deletion is hard or soft. It is barely an expansion of the tool name.

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 compact four-word phrase with no filler, and the key scoping word 'selected' is present. It is appropriately sized for a simple one-parameter tool, though it is close to the tool name and adds little structural value.

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 one-parameter tool with complete schema coverage, the description plus schema specify the action and input adequately. However, the destructive and high-impact nature of bulk deleting users is understated, and there is no safety hint from annotations or output schema.

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 coverage is 100% and the single userIds parameter is already clearly described as 'Array of user numeric IDs to delete'. The description adds no extra parameter meaning, so the baseline 3 applies.

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 clear action ('Bulk delete') and target ('selected users'), and the input schema scopes it to explicit user IDs. It is minimally distinguishable from siblings like users_delete and users_bulk_delete_by_status, though it never names them.

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 phrase 'selected users' implies using this tool when you have a concrete set of user IDs to delete, which is reasonable. However, there is no explicit guidance about when to prefer this over users_delete, users_bulk_delete_by_status, or other bulk variants.

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