pointsbet_sport_competitions

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

No annotations provided, so description carries burden. Discloses return structure and locale grouping, but lacks info on potential side effects, rate limits, or data freshness. For a read-only tool, this is minimally adequate but not exhaustive.

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?

Concise single sentence for purpose, followed by return structure and example. Front-loaded and efficient, though the return structure could be integrated more fluidly.

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?

Provides return structure and example, but lacks details on locale names, pagination, error handling, and how to find valid sportKey. Adequate for basic understanding but not fully self-contained for robust agent use.

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 0% and description does not explain the sportKey parameter beyond its name. The example with 'AFL' hints at usage, but no format or valid values are given. Adds little value over the schema.

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?

Clearly states the tool returns competitions for one sport, grouped by locale, with a return structure example. Distinguishes from siblings like pointsbet_competition_events or pointsbet_sport_featured_events by specifying the grouping and output shape.

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?

Implies use when needing competitions per sport with locale grouping, but does not explicitly state when to use this over alternatives like pointsbet_competition_events or how to obtain valid sportKey values. No mention of exclusions or prerequisites.

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