get_odds

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

No annotations exist, so the description carries the full burden. It discloses pagination behavior (hard when unscoped) and that it returns a flat array. However, it does not mention whether the operation is read-only, authentication needs, rate limits, or data freshness. For a query tool, these are useful but not critical gaps.

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 sentences, each with a clear purpose: what it does, usage warning, pagination instruction. No redundant words. Front-loaded with the core purpose.

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, so the description must convey what is returned. It says 'flat array of book prices' but doesn't detail the fields in each price object. However, the scoping and pagination are well covered, and the tool is core enough that users can infer the structure from context. Minor gap.

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 coverage is 100%, so baseline is 3. The description adds value by explaining the concept of 'scoping' and warning about unscoped calls, which goes beyond the parameter descriptions in the schema. It also references related list tools (list_markets, etc.) for valid values.

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 it returns 'a flat array of book prices' and lists the scoping dimensions (event_id, player_id, etc.). It distinguishes from siblings like get_event_odds by being more general. The verb 'returns' and resource 'book prices' are specific.

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?

Explicit guidance is given: 'prefer scoping to at least one entity' to avoid hard pagination, and 'Paginate with cursor' with reference to nextCursor. This tells when and how to use the tool effectively.

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