betfair_event_timelines

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

Annotations already declare readOnlyHint, openWorldHint, and idempotentHint, so the security profile is covered. The description adds useful context beyond annotations: the return format (a top-level array with nested score structure) and 'Auth: none needed,' which are valuable for an agent. No contradictions with annotations.

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 concise and well-structured: a one-sentence purpose, a return format snippet, and an auth note. Every sentence provides unique value with no redundancy or padding.

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?

No output schema exists, but the description compensates by explicitly listing the return shape. It covers the essential aspects: what data is returned, that it is a top-level array, and that auth is not needed. For a simple batch read tool, this is complete.

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%, with parameters already documented. The description's reference to 'several ... at once' aligns with the eventIds array parameter but adds no additional syntax or constraints beyond what the schema provides. Thus baseline 3 is appropriate.

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 the purpose: 'Live timelines + running scores for several in-play events at once (batch).' This specifies the verb (returns live timelines/scores), resource (in-play events), and scope (several at once), distinguishing it from the singular sibling tool betfair_event_timeline.

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 makes the batch use case clear ('several in-play events at once'), implying it is for when you need multiple timelines in one call. It does not explicitly mention alternatives or exclusions, but the batch context is sufficient for an agent to select it over the singular variant.

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