sportsbet_upcoming_events

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

No annotations provided, and the description does not disclose behavioral traits such as read-only nature, rate limits, authentication requirements, or side effects. The return format is provided but does not compensate for missing behavioral context.

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 concise with two sentences: first explaining purpose, second showing return structure. It is front-loaded and efficient, though could be slightly more structured with parameter info.

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?

Given no output schema and missing parameter descriptions, the description is incomplete. While purpose is clear, the agent lacks critical information about input parameters and behavioral context for proper 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 0%, and the description does not mention the two parameters (maxEvents, includePrimaryMarket) at all. The agent receives no guidance on their meaning or effect, relying solely on the schema's type and default 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 states 'Upcoming sport events across all codes (homepage upcoming feed)', which clearly indicates the tool retrieves upcoming events for all sports. It distinguishes from sibling tools like sportsbet_competition_matches and sportsbet_event_markets, which are more specific. However, it lacks a strong verb like 'list' or 'retrieve'.

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. The description only states what it does, with no exclusions, prerequisites, or mention of sibling tools for comparison.

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