get_matches

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

No annotations provided, but description discloses key behavioral traits: pagination is non-functional, no continuation token returned, and the raw parameter returns FIFA's untouched payload. Gives enough transparency for safe invocation.

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?

Extremely concise—two sentences with zero wasted words. Front-loaded with purpose, immediately followed by actionable usage details. Every sentence adds value.

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 list tool with no output schema, the description covers key return content (fixtures, kickoff times, final scores) and pagination caveat. Could mention sorting or limit defaults, but sufficient for agent understanding.

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 43%, but the description adds meaning for required parameters (idCompetition, idSeason) and optional narrowing (idStage, idGroup). Also explains count as pagination control and raw as payload toggle. Some schema parameters (like idStage, idGroup) remain minimally described.

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 it lists a competition's matches, including fixtures, kickoff times (UTC), and final scores for a season. It specifies required parameters (idCompetition + idSeason) and differentiates from siblings like get_live_match by focusing on list retrieval.

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?

Provides explicit context on when to use (listing matches for a season) and how to narrow results with idStage/idGroup. It also gives important pagination advice (pass large count for full list, no continuation token). However, lacks explicit when-not alternatives.

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