Get games played in a given month

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

No annotations are provided, so the description must fully disclose behavioral traits. It mentions what is returned (all games) but fails to address authentication requirements, rate limits, pagination, or any side effects. Minimal disclosure for a mutation-free tool.

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 concise sentence (14 words) that front-loads the action. No unnecessary verbiage, but structure is minimal as it lacks bullet points or groupings for clarity.

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 no output schema and 3 required parameters, the description is too brief. It does not explain what the return format is, whether results are paginated, or any error conditions. Incomplete for a tool with these characteristics.

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?

Description offers no additional meaning beyond parameter names (username, year, month). With 0% schema description coverage, the description should provide format or constraints but does not. Parameters are left to be interpreted from names alone.

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?

Description explicitly states 'All games (rated + casual, all formats) a player completed in a specific year/month.' It clearly identifies the resource (games by month), the verb (get), and the scope (all formats, rated and casual), distinguishing it from siblings like chess_get_current_games (current games) and chess_get_game_archives (archives).

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 historical game retrieval but provides no explicit guidance on when to use this tool versus alternatives, nor does it mention prerequisites or exclusions. Usage is implied but lacks clarity on appropriate contexts.

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