external_squads_add_all_users

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

With no annotations, the description carries the full burden of behavioral disclosure. It does reveal that the operation is asynchronous via '(async 202)', which is useful, but it does not explain what this means for the caller (e.g., no immediate result, need for polling), nor does it mention side effects, reversibility, or permission requirements. For a mutation tool, this is a significant gap.

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 description is a single, front-loaded sentence with no wasted words. The key scope ('ALL users') and the notable async behavior are both included, making it appropriately concise for a one-parameter tool.

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?

The tool is a mutating operation with no annotations, no output schema, and an async result, yet the description only states the action and the HTTP status code. It does not explain what the caller should expect after the 202 response, whether users are added immediately or eventually, or how failures surface. This is incomplete for safe invocation.

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 100%, so the single parameter squadUuid is already documented as 'Squad UUID'. The description adds no parameter-level meaning beyond this, but it also does not need to because the schema fully covers the only parameter.

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 description states a specific verb ('Add'), a precise scope ('ALL users'), and a distinct resource ('external squad'), immediately distinguishing this from squads_add_all_users and targeted add operations. It is more informative than the tool name alone and clearly specifies what the operation accomplishes.

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 guidance about when to choose this tool over alternatives or when not to use it. It does not mention that non-all user additions require a different tool, nor distinguish this from squads_add_all_users. The behavior is implied but not explicitly framed relative to sibling tools.

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