betfair_event_timeline

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

Annotations already state readOnlyHint=true, idempotentHint=true, and openWorldHint=true. The description adds valuable detail beyond annotations by showing the return shape (nested score, timeElapsed) and stating 'Auth: none needed'. No contradiction 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 compact and front-loaded: purpose in the first line, return example in the second, and auth in the third. Every part contributes useful information with no wasted words. The multiline return sample is structured and easy to parse.

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 moderate complexity (6 params, 100% schema coverage, no output schema, but with readOnly/idempotent annotations), the description covers purpose, return shape, and auth. It does not mention rate limits or error cases, but for a straightforward read-only tool, this is largely 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 schema descriptions cover all 6 parameters (100% coverage), including eventId as 'Single event id'. The description's mention of 'one in-play event' aligns with the schema but adds no deeper parameter semantics or new constraints beyond what the schema already provides.

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 'Live timeline + running score/state for one in-play event', specifying the resource and singular scope. It differentiates from sibling tools like betfair_event_timelines by focusing on a single event, but lacks an explicit verb like 'Get' and does not name alternative tools.

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 phrase 'for one in-play event' implies when to use the tool, but there is no explicit guidance on when not to use it or which alternative to choose. Sibling tools such as betfair_scores or betfair_event_details exist but are not referenced, leaving the agent to infer usage context.

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