sportsbet_racecard

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

With no annotations, the description provides basic behavioral info (returns racecard data) and a return format. However, it does not mention error handling, data freshness, authentication needs, or any restrictions, leaving gaps for a racing data tool.

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 extremely concise: two sentences covering purpose and return format. No redundant information; every sentence 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 tool's complexity (2 params, no output schema, no annotations) and numerous sibling tools, the description is incomplete. It lacks parameter explanations, usage guidance, and behavioral details needed for effective agent selection and invocation.

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 0%, yet the description does not explain the 'eventId' or 'selectionNames' parameters. 'eventId' is implied as the race identifier, but 'selectionNames' (boolean, default null) is completely unexplained. The description fails to add meaning 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 'Racecard for one race: runners, prices, scratchings' and includes a return structure, making the purpose evident. It distinguishes from related tools like 'sportsbet_multiple_racecards' by specifying 'one race', but does not explicitly contrast with siblings, preventing a 5.

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?

No guidance on when to use this tool vs alternatives like 'sportsbet_multiple_racecards' or 'sportsbet_racecard_with_context'. The usage context is only implicit (when a single racecard is needed). No exclusions or prerequisites beyond the required 'eventId' param.

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