external_squad_reorder_external_squads

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

No annotations are provided, so the description carries the full burden. The 'POST' prefix implies mutation, but the description does not disclose what gets destroyed, whether the item list must be exhaustive, whether omitted squads lose their position, or what authorization is required. The confirm-parameter behavior is documented in the schema, not the description.

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 method and route, but the trailing 'Tags: External Squads Controller' is auto-generated filler that adds no value, and the core purpose line is a bare restatement with no detail.

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 mutation tool with nested object parameters, no annotations, and no output schema, the description is inadequate. It omits payload semantics, ordering behavior, and error/confirmation expectations that an agent would need to invoke it correctly.

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 coverage is 50%: only the confirm parameter is described in the schema, while the nested body/items structure (uuid + viewPosition) is undocumented. The description adds nothing about how to construct the reorder payload, so 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?

States a specific verb (reorder) and resource (external squads), which is enough to distinguish it from the get/create/delete external squad siblings. However, it never explains what reordering means operationally (view positions), so the agent must infer intent from the name alone.

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?

The description gives no when-to-use guidance, no prerequisites, and no mention of the sibling reorder tools (internal_squad_reorder_internal_squads, config_profile_reorder_config_profiles). The only context is the HTTP verb and route.

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