get_all_premium_odds

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

With no annotations, the description must carry disclosure burden. It only adds 'paginated', which is already implied by the page and per_page parameters. No mention of read-only, destructive actions, rate limits, or response structure. Minimal behavioral insight beyond schema.

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?

Single sentence efficiently conveys core functionality and pagination. No unnecessary words, front-loaded with verb and resource. Every part adds value.

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, so description should provide expectations. It mentions 'odds' but lacks detail on underlying data structure, default pagination, or filtering behavior. Adequate for a simple list but not fully informative for complex queries.

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 all parameters documented. Per rule, baseline is 3 since description adds no additional meaning beyond schema. Parameters like include, select, filters are adequately explained there.

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?

Description clearly states 'Get all premium pre-match odds (paginated)'. Verb 'Get' and resource 'all premium pre-match odds' precisely define the action and scope. The term 'premium' distinguishes it from sibling get_all_prematch_odds, and 'paginated' indicates data retrieval pattern.

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?

No guidance on when to use this tool versus alternatives like get_premium_odds_by_fixture_id or get_all_prematch_odds. The description only states what it does without any context on selection criteria or when filtering is needed.

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