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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety/side-effect profile is covered. The description adds the pagination trait (opaque cursors yielding older pages), which is useful behavioral context, but it omits anything about rate limits, ordering guarantees, or result windowing.

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 compact sentence that front-loads the purpose and follows with the pagination workflow. Every clause carries load; nothing is redundant padding.

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, return values need not be described, and the two required parameters are fully documented. The description covers purpose and pagination adequately; only minor extras like ordering or freshness of results are 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 explains both team_id and the opaque cursor. The description's cursor guidance largely restates the schema's own wording, adding no new format or constraint detail. Baseline 3 applies.

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: 'paginated team match history' for a team. An agent can tell this returns a team's past matches rather than current settings or news. It does not explicitly contrast with sibling tools like fotmob_team, but the resource is unambiguous.

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?

Gives an explicit entry point ('start from fixtures.previousFixturesUrl in fotmob_team') and the pagination pattern ('pass each previous cursor for older pages'). Clear context for how to drive the call, though it offers no when-not-to-use or alternative-tool guidance.

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