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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so safety is covered. The description adds real behavioral context beyond that: prices are live, currency is US$, coverage spans leagues/Line Moves/Storylines, and the free CC BY 4.0 API is included — useful for interpreting the response without an output 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?

Two sentences, front-loaded with the resource and its price focus, then a compact payload enumeration, then the use cases. The parenthetical coverage list is dense but every element (leagues, Line Moves sports, Storylines competitions) carries distinct information an agent cannot get elsewhere.

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 zero-parameter read-only listing with no output schema, the description adequately explains what each returned product record contains (price, contents, coverage, purchase page) and mentions the free CC BY 4.0 API. Minor gaps remain around price freshness or pagination, though neither is likely material for a small catalog.

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 tool takes zero parameters and the schema is empty, so there is nothing to disambiguate and baseline 4 applies. The description correctly implies a full-catalog, unfiltered listing rather than any parameterized query.

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?

States a specific resource (Bet Better Data product catalog with live US$ prices) and enumerates its contents: price, plan contents, coverage, and purchase/info page. It is clearly distinguishable from sibling data tools like get_line_moves or get_storylines_on_sale, though it never explicitly names the closest sibling, get_my_plan.

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?

Provides concrete trigger questions — 'what does it cost' and 'which plan do I need' — which give an agent a clear signal for selection. It stops short of an exclusion clause, e.g. telling the agent to use get_my_plan instead when the question is about the caller's existing subscription.

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