external_squad_remove_users_from_external_squad

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

With no annotations, the description carries the full behavioral burden, yet it only restates the HTTP call. It omits that the operation is destructive/bulk, whether removals are reversible, what permissions are needed, and — most importantly — the preview-only behavior when confirm is absent (that detail exists only in a Russian-language schema description).

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?

Very short and front-loaded with the verb and resource, but the raw HTTP path and the 'Tags: External Squads Controller' line are autogenerated noise that consumes part of an already minimal description.

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, unannotated bulk mutation with no output schema, the description should explain the confirmation/preview flow and what 'remove users' operates on. Neither appears, so an agent could invoke it without realizing the call is a dry run and may be missing a user-list argument.

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%, so baseline 3 applies; the uuid and confirm parameters are documented in the schema. However, the description adds nothing beyond the endpoint, and it is silent on how the target users are identified for a 'remove-users' bulk endpoint, which is not clarified anywhere in either field.

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 specific verb and resource ('Delete users from external squad') and includes the exact HTTP method and path, so the action is unambiguous. It does not explicitly distinguish itself from close siblings like external_squad_delete_external_squad (whole squad) or internal_squad_remove_users_from_internal_squad, though the name and path make the scope inferable.

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?

No guidance on when to use this versus external_squad_update_external_squad or the add-users counterpart, and no mention that this is a bulk operation requiring a user list. The critical precondition that confirm:true must be passed for the request to actually execute is never surfaced in the description.

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