betr_next5_races

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

The description discloses the return format in detail, showing the structure of the items. This is good for a read-only tool. However, no annotations exist, and the description does not mention any side effects, authentication, or dynamic behavior like time-to-jump updates.

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 plus a return format spec. No unnecessary words. The core action is front-loaded. Ideal length for a simple tool.

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 simplicity (2 optional integer parameters, no output schema, no annotations), the description covers the essential information: what it returns and the filter criteria. It could be improved by noting the default values' meanings and that it returns approximately 5 races, but overall it is sufficient.

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 description adds meaning by stating the parameters are for 'race-type + country filter', beyond the schema which only provides integer types and defaults. However, it does not explain the mapping of integer values (e.g., 0 for all countries, 7 for horse racing), limiting the agent's ability to use them correctly.

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 returns 'Next races about to jump, with time-to-jump, for a race-type + country filter.' It specifies the resource (next races) and action (list with time-to-jump). However, it does not explicitly mention the count '5' as implied by the tool name, which could cause slight 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?

No guidance is provided on when to use this tool versus siblings like betr_todays_races or betr_race. The description implies it is for upcoming races with specific filters, but does not explain scenarios where alternatives are more appropriate.

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