sportsrc_get_live

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

No annotations provided. The description mentions client-side filtering but does not disclose rate limits, authentication needs, or whether the feed includes all matches or only upcoming ones. It only implies behavior via 'data array' and 'status' field.

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 long, front-loaded with the purpose, and contains no extraneous information. Every word earns its place.

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 input schema (one parameter) and no output schema, the description is adequate but incomplete. It mentions 'data array' and 'status', but does not describe the structure of matches or any other fields. Could be more comprehensive for a tool with many sibling tools.

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 description coverage is 100% for the single parameter 'category', which already includes example values and a reference to sportsrc_get_sports. The tool description adds no further meaning beyond the schema's parameter description.

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 gets a matches feed for a sport using 'get the matches feed for a sport' and mentions client-side filtering for live games. However, it does not explicitly differentiate from sibling tools like sportsrc_get_matches, leaving some ambiguity.

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 for live games via client-side filtering but does not state when to use this tool over alternatives like sportsrc_get_matches or sportsrc_get_league_scores. No explicit when-to-use or when-not-to-use guidance.

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