fotmob_player_stats

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

With no annotations provided, the description carries the burden of behavioral disclosure. It communicates that the tool returns rich statistics and that season_id is player-specific and discoverable elsewhere. It does not describe output format, pagination, data freshness, or explicitly confirm read-only behavior, but 'Returns' and the stats-domain context make the operation reasonably transparent.

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 description is compact and front-loaded: it states what the tool returns, then gives the essential discovery step for the non-obvious parameter. The first phrase is somewhat redundant with the tool name, but every sentence otherwise earns its place.

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 read-only stats endpoint with two well-documented parameters and no output schema, the description is largely complete: it names the main output categories, explains the season_id prerequisite, and flags player/season variation. A bit more detail on the response structure or hasDeepStats role would round it out.

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?

The schema already documents both parameters with 100% coverage, so the baseline is 3. The description adds useful operational context by pointing to statSeasons for season_id discovery and warning that entry ids vary by player and season, but it does not add detailed syntax or format guidance beyond what the schema provides.

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 the resource ('FotMob player season statistics') and a specific verb ('Returns'), and lists concrete outputs: deep statistics, shot map, heatmap, and goalkeeper shot map. It is clear that this is season-level data for one player-specific season entry, which helps distinguish it from match-level or player-overview siblings, though it does not name alternatives 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?

The description gives a clear prerequisite: valid season_id values and hasDeepStats should be discovered from '/fotmob/player statSeasons', and notes that entry ids vary by player and season. This tells the agent how to prepare inputs, but it does not explicitly state when to use this tool instead of related player/match stat tools.

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