internal_squad_add_many_users_to_internal_squad

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

No annotations are provided, so the description carries the full burden. It reveals only that the operation is a POST, and says nothing about the destructive/mutating nature, the 1000-user cap, partial-failure behavior, or the fact that the request is only previewed until confirm:true is supplied.

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 endpoint, which is mildly useful for API mapping, but the 'Tags: Internal Squads Controller' line is framework noise that earns no place. Brevity here reflects under-specification rather than disciplined conciseness.

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 mutating bulk operation with a nested body, no annotations, no output schema, and low schema coverage, the description omits the confirm-preview flow, the maxItems limit, and error/rollback behavior. An agent could invoke it correctly only by reading the schema closely rather than the description.

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%: userIds and uuid are undocumented in the schema, and the description adds no meaning to either. The critical constraints (1-1000 numeric user IDs, required uuid) are discoverable only by reading the raw schema, and the confirm/preview semantics documented in the schema are not surfaced in the description.

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 includes the underlying route, so an agent knows exactly what it does. It does not, however, distinguish itself from the near-identical sibling internal_squad_add_users_to_internal_squad (singular) or route to internal_squad_remove_many_users_from_internal_squad, leaving the many-vs-single distinction to inference.

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 at all. With a sibling that adds users one at a time and a sibling that removes many users, the description never says when bulk-add is the right choice, nor does it mention prerequisites such as confirmation.

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