end_turn

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

No annotations provided, but description discloses mutating nature, automatic waiting of units, and immediate opponent turn start. This adds behavioral context beyond a simple 'end turn'.

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?

Four sentences, each adding value. Front-loaded with 'Mutating' to indicate side effects. No redundancy or filler.

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 simple turn-ending action, the description covers purpose, usage, and side effects. However, the lack of parameter documentation is a significant gap, especially with no output schema to aid understanding.

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 single required parameter 'connection_id' has zero schema description coverage, and the tool description does not explain its meaning, purpose, or how to obtain it. The agent is left guessing.

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 uses a specific verb 'end' and resource 'turn', clearly stating the action. It distinguishes from siblings like 'wait' and 'concede' by naming the specific game action.

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 states when to call: exactly once per turn after all move/attack/heal/wait commands. Also notes error condition for wrong turn. Lacks explicit naming of alternative actions if not ready.

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