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

With no annotations provided, the description does substantial work: it explains that existing bots keep their positions, defines 'flip' versus 'drain' exit behavior, states that arriving bots follow normal fund rules, notes rejected bots appear in the result, and clarifies that the rationale is published publicly. It omits permissions, cost implications, and reversibility, which keeps it from a 5.

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 reasonably sized and front-loads the core action before explaining mode semantics and downstream effects. Some phrasing, such as 'the manager's main move,' is stylistic rather than informational, but overall there is little waste.

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?

An output schema exists, so return-value detail is not required. For a mutation tool with no annotations, the description covers the key state changes and side effects (positions retained, exit modes, rejected bots, public rationale). It is still missing authorization or cost prerequisites that an agent might need before invoking it.

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 0%, so the description must compensate. It explains the 'mode' values ('flip' closes at market now; 'drain' lets bots exit on their own rules) and the purpose of 'rationale' as a public manager log entry, but it does not clarify fund_id or formation_id beyond their names.

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 action (putting/switching a formation on the field) and frames it as the manager's main move. However, the phrasing is somewhat metaphorical and does not explicitly distinguish it from close siblings like update_formation or swap_bot_in_fund.

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?

It implies this is the primary managerial action and explains the mode choice between 'flip' and 'drain'. But it gives no explicit guidance on when to use this versus update_formation, swap_bot_in_fund, or create_formation, nor any conditions or exclusions.

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