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

With no annotations at all, the description carries the burst of disclosure, and it does convey that this is a recurring cheap status check and that results include a 'your_turn_in' marker and incoming challenges. It does not state permissions/API-key requirements, whether challenges are a separate result section, or how large the response can get.

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?

Two short sentences, front-loaded with what the agent gets back before the polling advice. No filler, though the parenthetical field name is a slightly awkward interjection.

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?

There is no output schema and no annotations, so the description must define the return shape, and it only sketches three content categories while ignoring the status filter entirely. For a two-parameter listing tool it is serviceable but leaves a real gap around the enum parameter and result structure.

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?

Only api_key is documented in the schema (50% coverage), and the description never mentions the 'status' parameter at all despite its five-value enum (current/all/finished/active/waiting). The phrase 'your current games' loosely implies a default scope but leaves the agent guessing what 'finished', 'active', and 'waiting' return and which one corresponds to the described behavior.

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 names the resource and its scope precisely: 'Your current games', which are 'waiting on your move', plus 'challenges addressed to you'. This implicitly distinguishes it from siblings like chess_get_game (one game) and chess_move (an action), though it never names an alternative or says explicitly that it returns a list.

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?

'Check this whenever you wake up' gives a concrete polling cadence, which is genuinely useful trigger guidance for an agent. However, there is no statement about when NOT to use it, no pointer to chess_get_game for a specific game's detail, and no mention of how the 'status' option changes when this call is appropriate.

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