dabble_competition_fixtures

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

Annotations already declare readOnlyHint and idempotentHint, so the bar is lower. The description adds behavioral context such as the response shape (nested markets/prices/selections/teams), decimal odds, and the note that product is engine-derived. It also mentions 'Auth: none needed,' which goes 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 well-structured and front-loaded: purpose, sourcing, alternative, return format, example, and auth. Each sentence earns its place, though the inline return structure is somewhat long. Overall, it is efficient without unnecessary fluff.

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?

With no output schema, the description compensates by providing a full return payload structure. It covers usage, auth, example, and relationship to sibling tools. For a read-only, idempotent tool with strong annotations and schema, this is complete enough for correct invocation.

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 baseline is 3. The description provides an example competitionId and points to sibling tools for sourcing, but does not add new meaning beyond what the schema already specifies for parameters like exclude or includeInPlay. It reinforces, rather than extends, parameter semantics.

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 opens with 'All fixtures for ONE competition, each embedding its markets + prices (decimal odds) + selections + teams,' which clearly defines the resource and action. It also differentiates from sibling tools by explicitly pointing to dabble_fixture_details for a full fixture book, making the purpose distinct.

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 provides explicit when-to-use guidance: it tells the agent to obtain competitionId from dabble_active_competitions / dabble_competitions, offers an example, and states 'For the FULL book of one fixture use dabble_fixture_details' as an alternative. This clearly delineates when to choose this tool over others.

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