external_squad_get_external_squads

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

No annotations are supplied, so the description carries the full behavioral burden, yet it only dumps the raw HTTP method/path. It does not state pagination behavior, result ordering, auth/permission requirements, or whether the full squad list is returned. "GET" implies a safe read, but nothing is explicitly disclosed.

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 short and front-loads the intent, but it wastes space on a raw REST path and a "Tags: External Squads Controller" artifact that add no meaning for an agent. The useful content is a single clause.

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 zero-argument list tool this is minimally adequate, but with no annotations and no output schema the description should at least indicate whether the response is paginated or filtered, which it omits. It leaves the agent guessing about the shape and size of the result.

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?

The tool takes zero parameters, which is the baseline-4 case; there is nothing for the description to explain beyond what the empty schema already communicates.

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 says "Get all external squads", which names the resource and the list-all scope, but it largely restates the tool name and gives no differentiation from the sibling external_squad_get_external_squad_by_uuid or from internal_squad_get_internal_squads. An agent gets the gist but must infer how it relates to its siblings.

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 on when to use this versus get_external_squad_by_uuid or the internal-squad equivalents, nor any prerequisite or filtering context. Usage must be inferred entirely from the name.

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