squads_remove_many_users

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

Annotations declare readOnlyHint=false and destructiveHint=false; the description adds nothing about whether users are only detached from the squad, whether the change is reversible, or any limits/rate constraints. The bare word "Delete" sits in mild tension with destructiveHint=false, leaving the actual blast radius unclear to the agent.

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?

A single short front-loaded phrase with no filler, which is structurally sound. It is too under-specified to call efficient, though — brevity here comes at the cost of necessary detail rather than from tight writing.

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 mutation tool with two required parameters, 0% schema description coverage, and no output schema, the description should explain the identifier semantics and the effect of removal. None of that is present, so an agent cannot call this confidently without inspecting the 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 description coverage is 0% and the description supplies no parameter meaning. It never says that "uuid" is the squad identifier and "userIds" is the list of numeric user ids to detach, nor mentions the 1–1000 item bound enforced by 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?

"Delete many users from internal squad" gives a verb and resource, and the word "internal" implicitly separates it from the external_squads_* family. However, it largely restates the tool name and never clarifies what a "squad" removal means for the affected users (membership removal vs account deletion), nor distinguishes itself from squads_remove_all_users beyond the word "many".

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. The agent is not told when this is preferable to squads_remove_all_users or how it relates to squads_add_many_users, nor whether the squad uuid or user ids must first be resolved via squads_list/users_resolve. Only the general name implies the use case.

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