sportsbet_racing_top_jockeys

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

Annotations already declare readOnlyHint, openWorldHint, and idempotentHint, and the description does not contradict them. It adds value beyond annotations by disclosing the exact return shape ({jockeys:[{name, rides:[{eventId, selectionName}]}]}) and the auth behavior (works without a key; token unlocks more). This compensates for the missing output schema.

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 compact, front-loaded sentences: purpose first, then return shape, then auth. Every line earns its place and there is zero filler or repetition of annotation data.

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?

For a zero-parameter, read-only tool, the description is nearly complete: it states scope, provides a return structure (important since no output schema exists), and clarifies auth requirements. Minor gaps include no example values, no pagination or size limits, and an unspecified meaning of 'more' with the token, but none are critical for a no-arg list call.

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 tool has zero parameters, so there is nothing for the description to clarify beyond what the empty input schema shows. Baseline 4 for a parameterless tool applies; the auth note (SPORTSBET_REFRESH_TOKEN) is the only relevant environmental input and is already disclosed.

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 identifies the resource — top jockeys and their rides today — and the 'Returns:' line makes the verb explicit. However, it does not explicitly differentiate from sibling tools; it relies on the tool name and domain to distinguish itself from racing tools like sportsbet_racing_best_bets or sportsbet_racecard.

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 'today' scoping and 'hub' phrasing imply it is for current-day leading jockey information, and the auth note gives practical guidance on when it can be called without a key. But there is no explicit when-to-use versus alternatives guidance, no exclusions, and no mention of what 'more' the refresh token unlocks.

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