fotmob_player_matches

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

With no annotations present, the description carries the burden of explaining behavior. It discloses that only one page is returned, that pagination requires a specific upstream value, and that filter availability depends on data from /fotmob/player. This goes beyond the schema and gives an agent practical expectations for call sequencing.

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 short sentences deliver the core purpose, the required upstream dependency, and the pagination mechanism without wasted words. The key fact that this returns one page is front-loaded.

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 moderately complex paginated tool, the description covers the required player_id, optional filtering constraints, the upstream discovery step, and pagination. There is no output schema, and the return payload is not described, but an agent has enough information to invoke the tool correctly and navigate pages.

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 all four parameters in detail. The description adds contextual value by linking team/league filters to fotmob/player matchFilters and clarifying the pagination parameter's origin, but it does not substantially extend the schema's meaning.

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 clearly states the tool returns one page of player match history, which is a specific verb-plus-resource statement. It is distinct from neighboring fotmob tools in meaning, though it does not explicitly name or contrast a sibling such as fotmob_player_match_stats.

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 useful workflow context: matchFilters and valid league/team pairs come from /fotmob/player, and pagination is handled by copying the numeric before timestamp from the upstream previous URL. It does not explicitly say when not to use this tool versus alternatives, but the usage context is clear.

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