sportsbet_upcoming_events

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

Annotations already indicate read-only, open-world, and idempotent behavior. The description adds valuable behavioral context beyond that: it works without an API key, states that a refresh token can unlock more data, and provides the exact response shape.

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 compact and well-structured: one line for purpose, one line for return format, one line for auth. Every sentence adds useful information and the main purpose is front-loaded.

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 simple read-only tool with two optional parameters and no required inputs, the description covers the key invocation concerns: what it returns, whether auth is required, and that it spans all sport codes. It could be slightly stronger with explicit usage boundaries versus sibling tools, but nothing essential is missing.

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 input schema already fully documents both optional parameters, maxEvents and includePrimaryMarket, so the description does not need to repeat them. The description adds no parameter-level meaning beyond what the schema provides, which meets the baseline for high schema coverage.

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 the tool returns upcoming sport events across all codes, identified as the homepage upcoming feed. This is specific enough to distinguish it from event-detail or sport-specific tools, though it does not explicitly name any sibling it is not.

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?

The phrase 'homepage upcoming feed' and 'across all codes' gives useful context about when this tool is appropriate. However, there is no explicit guidance about when to prefer another tool, such as a sport-specific or competition-specific event endpoint.

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