move

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

Discloses mutating nature (first word 'Mutating.'), status changes, return type (updated unit state), and error conditions. With no annotations, description fully carries the behavioral disclosure burden.

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, front-loaded with keyword 'Mutating.' Each sentence adds value: purpose, conditions, parameter details, consequences, return, errors. Could be slightly more structured but efficient.

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?

Covers prerequisites, side-effects, return value, and error conditions. References get_legal_actions for range checking. No output schema but describes return as updated unit state. Sufficient for the tool's complexity.

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?

Explains unit_id as string identifier and dest as {x,y} dict. Connection_id is not explained despite being required and having no schema description. 0% coverage means description must compensate; it covers 2 of 3 parameters.

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 'Move one of your units to a destination tile' with specific verb+resource. Distinguishes from siblings like attack, heal, wait by specifying conditions and effects.

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 prerequisites: unit must be READY, destination must be within movement range (check via get_legal_actions). Also notes consequences: status changes to MOVED, can still attack/heal/wait but not move again. Lists error conditions for invalid moves.

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