list_states

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

No annotations are supplied, but "List" self-evidently implies a non-destructive read. The description says nothing about where states come from, whether they are scoped to the current game or session, or what the listing contains — though the output schema covers return shape.

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?

A single short sentence with no waste, and the operation is front-loaded. Nothing extraneous is present.

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-param read tool with an output schema, this is nearly adequate, but it leaves open whether states are global or tied to the current game/session — a distinction that matters given siblings like load_state and start_game.

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?

Zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies.

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?

Names a specific verb ("List") and resource ("save states"), which distinguishes it from save_state and load_state by implication. It never explicitly says how it differs from those siblings, so it stops short of a 5.

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?

Use is implied: an agent would list states to discover what is available before calling load_state. There is no explicit when-to-use statement, no mention of alternatives, and no note about scope (global vs. per-game).

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