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

Annotations already declare readOnly, idempotent, open-world and non-destructive behavior. The description adds useful context beyond annotations by disclosing the returned aggregates and recent-match listing, and by warning that team names must match Cricsheet's naming. It does not cover behavior when a team is unknown or ambiguous.

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 sentences, front-loaded with the core purpose and outputs, followed by naming guidance and optional scoping. No filler and every sentence contributes actionable 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?

With five parameters, no output schema, but full annotations, the description is nearly complete: it explains the output aggregates and the critical team-name convention. Minor gaps remain around unknown-team handling and exact-match expectations, but nothing essential for correct invocation 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?

Schema coverage is 100%, so the baseline is 3. The description adds meaningful semantics beyond the schema by explaining that team names must follow Cricsheet's conventions and by noting that omitting format searches across all formats, which helps avoid incorrect entity resolution.

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?

States a specific verb and resource: head-to-head record between two cricket teams, with enumerated outputs (total matches, wins, ties/no-results, recent matches). This aggregate summary is distinguishable from sibling tools like cricsheet_match and cricsheet_find_matches, which retrieve individual matches.

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?

Gives clear usage context: pass team names as Cricsheet uses them, with concrete examples, and optionally scope to one format. It does not explicitly state when to prefer this over cricsheet_find_matches or cricsheet_match, but the aggregate nature implies the use case.

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