Check Game Status

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

Annotations are all false and provide no guidance. The description clarifies it is a read-only query of game state, though it does not explicitly state lack of side effects. It adds value beyond annotations by listing what is checked.

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 a single sentence that is front-loaded with key details. No unnecessary words.

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?

Given the tool is simple with one parameter, the description sufficiently covers what the tool does and what it returns (elapsed time, tool calls, hints, score). No output schema is needed.

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 100%, so baseline is 3. The description does not add extra information about the session_id parameter beyond what the schema provides.

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 the tool checks elapsed time, tool calls, hints used, and current score. This is a specific verb + resource, and it distinguishes from sibling tools like look_around or inventory which have different purposes.

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?

The description implies usage for checking game progress, but does not explicitly provide 'when to use' vs alternatives or any exclusion criteria. Since the purpose is straightforward, it still gives clear context.

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