internal_squad_add_users_to_internal_squad

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

With no annotations, the description carries the full behavioral burden but only states the HTTP method (POST), implying mutation. It does not disclose the potentially massive side effect of adding every user to the squad, whether the action is reversible or idempotent, or any permission requirements.

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?

The text is short, but the opening raw HTTP path and the trailing 'Tags: Internal Squads Controller' are boilerplate that does not earn its place. The one meaningful clause is buried in the middle rather than front-loaded.

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 two-parameter mutating bulk operation with no annotations, no output schema, and half-documented parameters, the description is far too thin. It omits the critical fact that this affects all users and says nothing about the confirm/preview flow that the 'confirm' parameter enables.

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 50% (uuid has no description, only pattern/format). The description adds no meaning for either parameter and does not explain how uuid scopes the operation. It fails to compensate for the coverage gap.

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?

The verb+resource phrase 'Add all users to internal squad' identifies an operation, but it does not distinguish this tool from sibling 'internal_squad_add_many_users_to_internal_squad'. The leading line is just a raw HTTP path ('POST /api/internal-squads/{uuid}/bulk-actions/add-users'), so an agent cannot tell the 'all users' variant from the 'many users' variant without opening both schemas.

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, no prerequisites, and no mention of alternatives such as 'internal_squad_add_many_users_to_internal_squad' or 'internal_squad_remove_users_from_internal_squad'. The description offers no routing signal for choosing this over its near-siblings.

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