sports-scores

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

Without annotations, the description usefully discloses the data source (ESPN's free public API) and describes the return fields (game status, score, venue, period/clock, broadcast). It implies no authentication needed. No mention of rate limits, but the disclosure is substantial.

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?

Three sentences, each earning its place: first states purpose and scope, second describes return content, third mentions API source and one parameter nuance. Front-loaded with key info, 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?

Given the three simple parameters and no output schema, the description covers purpose, return fields, and a key parameter nuance (date filter). No missing critical information for typical use.

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 the date parameter allows querying historical or upcoming schedules beyond the schema's 'Date in YYYYMMDD format'. It repeats default for league but doesn't add to limit parameter.

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 tool returns live and recent sports scores for a specific list of leagues (NBA, NFL, MLB, etc.), which is a specific verb+resource. It distinguishes from siblings like 'sports-prediction' by focusing on scores rather than predictions.

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 usage (use for scores) and mentions optional date filter for historical/upcoming schedule, but does not explicitly state when not to use it or suggest alternatives among the many sibling tools. Guidance is adequate but not directive.

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