get_legal_actions

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

Starts with 'Read-only' and describes return structure. Discloses error behavior for inappropriate units. No annotations, so description carries burden; missing details like rate limits or authentication, but sufficient.

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 with no fluff. Key purpose first, then usage guidance, then error conditions. Front-loaded efficiently.

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?

No output schema, but description covers return values (tiles, enemy IDs, ally IDs, wait). Adequate for a query tool; includes prerequisites and error handling.

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 0%, but description clarifies unit_id as 'string identifier from get_state'. Adds meaning beyond schema, though connection_id is not explained.

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?

Clearly states it returns legal actions for a unit, listing specific action categories (movable tiles, attackable enemies, etc.). Distinguishes from sibling action tools like attack, move, heal, wait.

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 advises calling before move/attack/heal/wait to avoid errors. Specifies conditions (own units in READY or MOVED) and error cases (enemy units or already acted).

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