sm_livescores

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

No annotations are provided, so the description must carry the burden. It explains the three modes and suggests the include parameter, but does not disclose any side effects, permissions, response format, or limitations. The description essentially repeats schema information, adding only the general statement that include enriches data.

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 two sentences, front-loads the primary purpose, and packs the mode definitions and include guidance without extraneous 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 2-parameter tool with no output schema, the description adequately covers the core functionality and mode options. However, it omits any mention of the response structure or edge cases, leaving minor gaps for an agent expecting return value details.

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 schema already provides 100% coverage with detailed descriptions for both parameters. The description adds the phrase 'Use include param for enriched data,' which is a minor usage hint but does not introduce new syntax or semantics beyond the schema.

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 it retrieves live football/soccer scores and enumerates three distinct modes (inplay, all, latest), which differentiates it from sibling tools like sm_fixtures or sm_schedules that handle scheduled matches.

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 provides clear context for when to use each mode: 'inplay' for currently playing, 'all' for today's livescores, 'latest' for recently updated. It also hints at using the include parameter for enriched data, but it does not explicitly compare against alternative tools.

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