sportsrc: Get matches

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

Annotations already declare readOnlyHint, openWorldHint, and idempotentHint, so the description's role is reduced. It adds context that the output includes team info and covers live/upcoming/recent matches, which is helpful but not extensive. No contradictions with annotations.

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 a single, front-loaded sentence that efficiently conveys purpose and scope. Every part earns its place with no redundant words.

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 the simple parameter (category) and no output schema, the description provides adequate context by stating what the tool returns (matches with team info, statuses). It could mention additional fields like match IDs or scores, but it's sufficient for a list endpoint.

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?

The input schema has 100% coverage for the single parameter 'category', with a detailed description that includes example values. The tool description adds minimal additional meaning beyond 'list matches for a sport', so the baseline of 3 is appropriate.

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 verb 'List', the resource 'matches', and the scope 'for a sport'. It also specifies the types of matches returned (live, upcoming, recently finished) and includes team info. This effectively distinguishes it from other sportsrc tools like sportsrc_get_match or sportsrc_get_live.

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 lacks explicit guidance on when to use this tool versus alternatives such as sportsrc_get_league_scores or sportsrc_get_match. No when-not-to-use or context for selection is provided, leaving the agent without prioritization hints.

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