seriea_matches

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

Annotations already declare readOnly/idempotent/openWorld, but the description adds substantial behavioral context: the ~1.2 MB payload, that narrowing params are ignored, the need for client-side filtering, and the exact meaning of matchSet/roundName. It also states auth is not needed and outlines the return shape.

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 dense with essential information: purpose, size warning, filtering instruction, return schema, and auth. Each sentence or code snippet earns its place; the formatting with a separate note and code block makes it easy to scan.

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 tool with no output schema, the description fully explains the return structure, the matchweek grouping concept, and the client-side filtering requirement. It also addresses the large payload and how to source the required seasonId, making it highly complete for the tool's complexity.

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 100%, so baseline is 3. The description adds value by explaining that matchday/round/page parameters are ignored (even though they don't exist in the schema) and clarifying the seasonId comes from seriea_seasons. This goes beyond the schema descriptions.

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 'All 380 matches for a season' and lists the included fields (scores, status, kickoff, stadium, matchday). It is season-scoped and distinguishes itself from sibling tools like seriea_seasons, seriea_standings, and seriea_teams.

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 strong context: season-scoped, whole season returned, must filter client-side, and mentions seasonId comes from seriea_seasons. However, it does not explicitly name alternative tools or when not to use this one, so it stops short of a 5.

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