sportsrc: Get league scores

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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, covering safety and idempotency. The description adds that it returns scores/recent results but does not disclose limitations like time range or availability. 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?

A single sentence that is concise and front-loaded. No unnecessary 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?

For a simple tool with one param and no output schema, the description is adequately complete. It does not explain the return format, but annotations cover safety. Could mention if results are limited to recent ones.

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%, but the description adds value by explaining the 'league' parameter: 'League id (use sportsrc_get_leagues to list). E.g. 'PL', 'CL', 'BL1'.' This provides examples and hints to find valid ids.

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 'Get scores / recent results for a specific football league,' using a specific verb ('Get') and resource ('scores / recent results'). It distinguishes from siblings like sportsrc_get_live (live scores), sportsrc_get_match (single match), sportsrc_get_table (standings), etc.

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 implies when to use (want recent results for a league) but does not explicitly state when not to use or mention alternatives. However, the context of sibling tools provides some guidance.

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