sportsbet_event_markets

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

Annotations already declare readOnlyHint, openWorldHint, and idempotentHint, covering the safety profile. The description adds useful behavioral context by explicitly stating 'Auth: none needed' and specifying the return structure with 'live prices,' which informs the agent about data freshness and authentication requirements beyond the 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 extremely concise, front-loaded with the core purpose, and includes a compact return structure example. Every sentence serves a purpose: scoping, output format, and authentication. No unnecessary words.

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 simple read-only tool with one parameter and a well-defined return schema in the description, this is complete. The agent knows exactly what data to expect and in what shape, satisfying the information needs for this low-complexity tool.

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%, so the schema already documents eventId as required and part of the URL path. The description does not add further parameter meaning beyond what the schema provides, maintaining the baseline score for complete schema coverage.

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 tool's function: retrieving all markets, selections, and live prices for a single sport event. The verb 'returns' followed by specific resource components (markets, selections, prices) makes the purpose unambiguous and distinguishes it from event lists or results 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 description implies usage for a single sport event but does not explicitly state when to use this tool over alternatives like betfair_markets_by_event or tab_match_markets. No exclusions or alternative references are provided, relying on the reader to infer the intended context from the phrase 'one sport event.'

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