list_moves_detailed

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

No annotations are provided, so the description carries the burden. It discloses the return item structure (ply, side, uci, san) and uses 'Return' to imply a read-only operation. However, it does not mention ordering, empty-game behavior, or whether this is the full move history versus a subset, which would be useful behavioral context.

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 two short lines, front-loaded with the core action and immediately followed by the return format. Every sentence adds value and there is no redundant content.

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 no-parameter, simple read tool, the description is nearly complete: it states the purpose and the return item shape. The output schema exists, so further return-value explanation is unnecessary. It does not explicitly disambiguate from last_moves_detailed or list_moves, which is a minor gap.

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 tool has zero parameters and an empty schema, so parameter semantics are trivially satisfied. The baseline for 0 params is 4; no parameter description is needed.

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 clearly states 'Return detailed move history,' identifying the specific resource and the detail level. It does not explicitly contrast with siblings like list_moves or last_moves_detailed, but the word 'detailed' and the included item format provide some differentiation.

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?

No guidance is given about when to use this tool versus alternatives. Siblings include list_moves, last_moves, and last_moves_detailed, but the description does not explain whether this returns all moves, recent moves, or how 'detailed' compares to the other list tools.

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