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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds genuine behavioral detail beyond that: the metric-map return shape and the meaning of a not-found result ('SofaScore has no list for the sport right now'), which tells the agent how to interpret empty responses.

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 followed by the constraint and edge case. The parenthetical field list ('rating, minutes, goals and more') is slightly loose but earns its place by signaling the payload contents.

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 an output schema present, the description need not enumerate return fields, and it stops at a useful summary. Combined with the input constraint and error semantics, an agent has enough to invoke it correctly, though sibling disambiguation is the remaining gap.

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% and the single parameter is already documented as 'Required. One of football, basketball.' The description restates the same allowed values without adding format, casing, or fallback guidance, so it neither compensates for nor exceeds the schema.

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 ('Returns a sport's trending top players') and defines what trending means ('standouts from recent matches'), which is more than the name conveys. It does not, however, distinguish this from near-neighbors such as sofascore_team_top_players or sofascore_tournament_top_players, so an agent must infer the boundary.

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?

The description constrains inputs ('Requires sport football or basketball') and explains the empty-result case, which is helpful context. It never states when to prefer this over the sibling top-player or ranking tools, leaving selection to inference.

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