draftkings_league_events

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

With no annotations provided, the description carries the burden and does well by disclosing that this is a public event directory, that results include availability tags, and that it deliberately excludes betting markets and odds. It stops short of 5 because it doesn't mention pagination, response formatting, or other operational limits.

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, front-loaded, and uses two sentences to cover what the tool returns, what fields are included, where the league_id comes from, and what is excluded. Every sentence earns its place.

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 single-parameter directory lookup, the description provides enough context: what to supply, where to source it, and what the response will contain. It does not describe pagination or a return structure, but the absence of an output schema is partially mitigated by the explicit field list.

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 100%, so a baseline of 3 applies, but the description adds real value by telling the agent exactly where to source a valid league_id from, which helps avoid invalid inputs. It reinforces that the ID is numeric and is a league-level identifier rather than an event-level one.

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 uses a specific verb and resource: it 'returns' a DraftKings Sportsbook league's current public event directory, and lists concrete returned fields such as event IDs, participants, start times, status, and availability tags. It also distinguishes itself from odds/market-focused tools by stating 'does not include betting markets or odds.'

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 description clearly explains how to obtain the required league_id from specific related endpoints, such as /draftkings/sportsbook/leagues and /draftkings/sportsbook/featured-leagues. It also signals when not to use this tool by excluding markets and odds, though it does not explicitly name sibling alternatives like draftkings_odds.

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