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 that the shot map is 'larger,' hinting at response-size cost, but does not elaborate on payload size, pagination, or auth needs beyond what the annotations and schema already convey.

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?

A single front-loaded sentence with no filler, and the sibling reference plus parameter hints are packed efficiently. It is slightly dense with three comma-joined clauses, but nothing is wasted.

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 covering return values and annotations covering the safety profile, the description supplies exactly the missing context an agent needs: how to obtain a season value and the size implication of shotmap. Nothing essential to correct invocation is absent.

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%, so the schema already documents season, shotmap, and league_id, including the allAvailableSeasons fallback and the size warning. The description reinforces the season and shotmap semantics but adds little beyond the structured fields, which is the expected baseline when the schema does the heavy lifting.

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 identifies the resource (FotMob league page sections) and names a sibling (fotmob_seasons), letting an agent distinguish it from the season-discovery tool. However, it uses a noun phrase with no explicit verb and leaves 'sections' undefined, so what data actually comes back is only partially clear.

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?

It gives explicit when-to-use guidance for two of the three parameters: use fotmob_seasons to discover season values, pass a listed season for historical data, and set shotmap=true for the optional overview map. It names the alternative for season discovery, though it does not state when to prefer this tool over other league-level siblings like fotmob_table or fotmob_stats.

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