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

Goes well beyond the readOnly/openWorld annotations: discloses the data sources (Kalshi public live feed, CricCenter for Atlanta Open T20), what is absent from the feed ('no ball-by-ball commentary and no batters or bowlers'), how win chances are derived (market midpoint only when the book is a real price, plus a server model with equal ratings), and fallback behavior when nothing is on.

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?

Front-loads the purpose effectively, but the remainder is a single sprawling run-on paragraph mixing data sources, field lists, and caveats. The content is largely useful, yet it is not structured for scanning and could be trimmed without losing meaning.

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?

No output schema exists, so the description carries the return-value burden and does so thoroughly: state, start time (ET), score, chase requirement or result, both win-chance sources, and the extra Atlanta Open T20 fields (toss, batters/bowlers, over in progress, innings performers, player of the match). Nothing needed to interpret results is missing.

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?

With 100% schema coverage and a single optional parameter, the schema already documents that a full or partial team name is accepted and that omitting it returns all games. The description repeats the 'omit for every game' semantics rather than adding new syntax or format guidance, so baseline 3 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 the specific resource (Minor League Cricket and Atlanta Open T20 scores and win chances) with a clear verb, and explicitly differentiates itself from cricket_minor_league_info by assigning that tool the league history/teams/grounds/players. An agent can route between the two without opening either schema.

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?

States the selection window precisely ('every game live, starting within 3 hours or finished in the last 2 hours, or one team's game') and names the sibling to use for static reference data. It implies when to use it clearly, but never states an explicit exclusion or edge-case alternative for this tool itself.

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