wait

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

No annotations provided, so description carries full burden. Discloses mutating nature, status change to DONE, and prerequisites. Could mention if this triggers any automatic opponent turn, but overall clear.

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?

Description is informative but a bit verbose; could be more concise. However, it is well-structured and front-loaded with the key verb 'Mutating.'

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?

Given the tool's simple action, no output schema, and no annotations, the description covers purpose, prerequisites, usage context, and next step completely.

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%; description only explains unit_id but not connection_id. While unit_id is described, connection_id is left unexplained, leaving partial parameter ambiguity.

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?

Description clearly states the tool ends a unit's turn without attacking or healing, setting status to DONE. It distinguishes from siblings like attack, heal, and end_turn.

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?

Explicitly says when to use: when a unit has no useful attack/heal targets but you want to finalize position after moving. Also specifies prerequisites (READY or MOVED status) and next step (call end_turn).

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