kaiten_batch_remove_sd_org_users

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It makes the destructive nature of the operation clear, but it does not disclose partial failure behavior, atomicity, irreversibility, permissions, or other side effects. This is a minimal mutating operation description with no added behavioral depth.

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 short sentence that front-loads the operation and object. It contains no filler and conveys the essential batch intent efficiently.

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 schema fully documents the required parameters, and the description states the core operation, so an agent can construct a valid call. However, with no annotations and no output schema, the description omits batch-specific caveats and consequences of removal, leaving some important context missing for a mutating tool.

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?

The input schema already describes both parameters with 100% coverage, including their types and roles. The description adds no additional meaning beyond the schema, 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 uses a specific verb ('Remove') and clearly identifies the resource ('multiple users from a Service Desk organization'). The phrase 'at once' distinguishes it from the singular sibling kaiten_remove_sd_org_user, so the tool's scope is immediately clear.

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 implies this tool is for batch removal by saying 'multiple users' and 'at once', which suggests when to prefer it over the singular removal tool. However, it does not explicitly name the alternative or provide exclusion criteria, so the guidance remains implied rather than direct.

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