seriea_matches

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

Despite no annotations, description fully discloses behavior: large ~1.2 MB payload, ignored server-side filters, and full return structure. No contradictions.

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?

Description is concise with key info front-loaded. Every sentence adds value, including the NOTE and return format. No unnecessary text.

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?

Given no output schema, description includes detailed return object. Behavioral transparency covers payload size and filtering limitations. Tool purpose is straightforward, and description is thorough.

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?

Only seasonId is implicitly explained via 'season-scoped'; locale is not described. Schema coverage is 0%, so description should cover both params; locale omission is a minor gap.

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?

Clearly states it retrieves all 380 matches for a season with specific fields (scores, status, etc.). Differentiates from siblings like seriea_match and seriea_season by explicitly noting season scope.

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 context: use for season-scoped matches, notes parameters like matchday/round/page are ignored, and advises client-side filtering. Lacks explicit exclusion for single-match use, but context is clear.

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