cricket_player_matchup

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), so the description is free to add the genuinely important disclosure: meta.estimated is true and this is a heuristic model, not ball-by-ball H2H data. That caveat materially changes how an agent should present results, and it goes well beyond the structured fields.

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 purpose is front-loaded in a single sentence, followed by a compact Args/Returns block with no filler. The Returns section is somewhat redundant given an output schema exists, but it is short enough not to be a real cost.

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?

For a simple two-parameter read tool with full schema coverage, an output schema, and rich annotations, the description covers purpose, inputs and the heuristic caveat. The only real omission is positioning against the cricket_head_to_head sibling, which matters for correct tool selection.

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% and the two Args lines simply restate the schema wording verbatim, including the 'names are not resolved' warning. No additional meaning (ID format, where to obtain IDs, behaviour on invalid IDs) is contributed beyond the schema, so the 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?

The description names a specific verb ('Analyse') and a specific resource ('head-to-head matchup between two cricket players'), and scopes it to role and career stats. It is clearly distinct from team/match-level siblings, though it never names cricket_head_to_head or cricket_player_form_index, so the differentiation is left implicit.

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?

There is no explicit when-to-use or when-not-to-use guidance and no reference to any alternative. Given the sibling list contains both cricket_head_to_head and cricket_player_form_index, an agent has to guess which tool the player-vs-player question belongs to.

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