squads_add_many_users

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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the baseline safety profile is covered. The description adds nothing beyond that: no mention of what happens to users already in the squad, whether the operation is idempotent, permission requirements, or the 1000-user cap.

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 tight sentence with the action front-loaded and zero filler. It is not bloated, though its brevity is partly the result of under-specification rather than disciplined editing.

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 bulk mutation with no output schema and 0% parameter coverage, the description should explain the squad/user identifier shapes and what a successful bulk add returns or does with duplicates. None of that is present, so an agent cannot call this confidently without guessing.

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 description must carry the parameter burden, and it only loosely implies that 'uuid' is the squad identifier and 'userIds' are numeric user IDs. It gives no format, ordering, or partial-failure semantics for the array, leaving both parameters materially under-documented.

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 ('Add many users to internal squad'), and the 'internal squad' qualifier separates it from the external_squads_* family. It does not explicitly distinguish itself from squads_add_all_users, but the 'many' vs 'all' wording carries the 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?

No when-to-use guidance, no prerequisites (e.g., squad must exist), and no mention of the obvious alternative squads_add_all_users or the inverse squads_remove_many_users. The agent must infer the selection criteria from the name alone.

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