internal_squad_remove_many_users_from_internal_squad

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

With no annotations, the description carries the full burden, yet it only restates the HTTP verb and route. It does not disclose that this is a destructive, irreversible bulk removal, that the confirm flag gates execution, that the operation caps at 1000 users, or what happens on partial failure.

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-loads the operation, but the raw 'DELETE /api/...' line largely duplicates the tool name and the 'Tags: Internal Squads Controller' line is pure noise. Two of three lines do not earn their place.

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 annotations, no output schema, a nested required body, and a confirm-gate the agent must know about, the description is far too thin. It omits the safety profile, the size limit, and the preview-without-confirm behavior.

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 33% (just the confirm flag, described in Russian), leaving uuid and body.userIds undocumented. The description adds no parameter meaning at all, so it fails to compensate for the coverage gap on a nested-body tool.

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 gives a clear verb+resource: 'Delete many users from internal squad', which an agent can match to the operation without opening the schema. It does not, however, differentiate from the sibling internal_squad_remove_users_from_internal_squad (singular) or explain the 'many' vs single distinction.

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 when-to-use guidance, no prerequisites, and no mention of the singular sibling internal_squad_remove_users_from_internal_squad as the alternative for single removals. The agent must infer selection entirely from the name.

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