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

Annotations already cover the safety profile (readOnlyHint=true, openWorldHint=true), so the bar is lower, and the description still adds real behavioral facts beyond them: results are scoped to the 'current' window and grouped by date and series, and the query filter is applied 'locally' to the returned set rather than as a server-side search. That local-filtering detail is exactly the kind of trait an agent needs, since it means a query cannot surface matches outside the current window; only rate limits/pagination behavior is absent.

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?

Three sentences, purpose front-loaded, then the parameter roles, then an actionable usage line. No filler, and the reader knows what it returns and how to narrow it before reaching the last sentence.

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 a full input schema, an output schema and read-only/open-world annotations, the remaining burden on the description is small, and it covers windowing, grouping and local-filter semantics. The one gap is routing — it never says how this differs from cricbuzz_matches or cricbuzz_archives, which matters given the dense Cricbuzz sibling set.

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%, with Category enumerating all/international/league/domestic/women and Query documented as a case-insensitive substring over series, match descriptions and team names. The description largely restates those schema facts, adding only the 'locally' qualifier, so baseline 3 is appropriate; it also uses 'q' while the parameter is named 'Query', a small mismatch the agent must reconcile.

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 concrete resource and shape — the Cricbuzz 'Matches By Day' window, grouped by date and series, returned as a dated fixture list. That clearly separates it from detail-level siblings like cricbuzz_scorecard or cricbuzz_match_facts, though it never names the nearest alternatives (cricbuzz_matches, cricbuzz_archives) so the boundary with 'live matches' versus 'past archives' is inferred rather than stated.

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?

'Use category and q to narrow the dated fixture list' gives parameter-level guidance but no tool-selection guidance — nothing says when to prefer this over cricbuzz_matches or cricbuzz_archives. Usage is only implied by the word 'current', which hints at the live window without stating it.

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