squads_remove_all_users

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

Annotations already declare destructiveHint=true and readOnlyHint=false, and the description's 'Remove EVERY user' is consistent with that. However, it adds nothing beyond the annotations: no note on irreversibility, whether the squad itself survives, or whether re-adding users is required to undo it.

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?

Two short sentences, the destructive scope front-loaded, and the sibling routing packed into the second. Nothing wasted.

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?

With one parameter, no output schema, and annotations carrying the safety profile, the description is nearly sufficient — but it leaves the uuid referent unclear and says nothing about confirmation requirements or failure behavior for a destructive bulk operation.

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%, so the single 'uuid' parameter is undocumented in both the schema and the description. For a tool that removes users, it is genuinely ambiguous whether uuid identifies the squad or a user; the description never resolves this.

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 ('Remove'), resource ('users from an internal squad'), and scope ('EVERY'), which lets an agent distinguish it from squads_remove_many_users without opening either schema. The emphasis on 'EVERY' plus 'internal squad' also separates it from external_squads_remove_all_users.

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?

Explicitly names the alternative tool and the condition that selects it: bulk-selective removal belongs to squads_remove_many_users, this one is for wiping the entire squad. That is the exact decision an agent has to make.

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