squiggle_get_games

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

No annotations provided, so the description bears full burden. It lists return fields but does not disclose behavioral aspects like read-only nature, rate limits, or data freshness. The description adds limited behavioral context beyond what the parameter schema implies.

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, efficient sentence of 15 words. It is front-loaded with the action and resource, with no redundant information.

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, the description adequately enumerates major return fields (teams, scores, status, venue, time). It misses potential details like ordering or pagination, but for a filtered list tool with 4 optional parameters, it provides sufficient context.

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 description coverage is 100%, so the schema already documents all parameters. The description confirms the tool returns specified fields but does not add new parameter-level meaning beyond the schema (e.g., the 'team' parameter's helpful reference to squiggle_get_teams is already in the schema).

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 it retrieves AFL games with optional filters and lists specific return fields (home/away teams, scores, completion status, venue, time). This distinguishes it from sibling tools like squiggle_get_teams or squiggle_get_ladder.

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 mentions optional filters, implying general usage for fetching games. It does not explicitly state when to use this tool vs alternatives or when not to use it, but the context is clear among the sports query tools.

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