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

Beyond the readOnly/idempotent annotations, the description discloses real behavioral detail: rates only appear after 50 matches, a too_few_matches reason is returned before that, and National is a rolling 8-week window ranked on the prior 8 weeks. It does not discuss payload size, pagination or caching, but the data-availability semantics are unusually well covered.

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?

Purpose is front-loaded and every clause carries substantive information about metrics, windows or thresholds. It is dense — long compound sentences pack metric definitions, ranking windows and the minimum-match rule together — so it reads heavier than it needs to, but there is essentially no filler.

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?

There is no output schema, so the description must define the return fields, and it does: majorityCorrect, outcomeCorrect and exactCorrect are each defined, including the exactCorrect National-only caveat. Combined with the availability rule and filter guidance, an agent has enough to call and interpret the tool correctly.

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 would be 3, but the description adds cross-parameter meaning the schema lacks: 'competition' is the National league name and 'game' applies to Classic, making the mode pairing explicit. That interaction constraint is genuinely useful context an agent would otherwise have to infer from enum descriptions.

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 opening clause states exactly what is returned: per-group accuracy rates for TipMaster football predictions, with the three metrics named (majorityCorrect, outcomeCorrect, exactCorrect). It is clearly an aggregate-accuracy tool rather than a pick or match lookup, so it is distinguishable from siblings like get_expert_picks and get_consensus by intent, though no sibling is named explicitly.

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?

Usage is implied rather than prescribed: it explains the National vs Classic windows and says 'Pass competition ... or game ... to narrow it', which tells the agent how to filter but not when this tool is preferable to get_consensus or get_match_prediction. No exclusions or preconditions for choosing among siblings are given.

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