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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds genuine context beyond that: the shortcuts are home-page curated (not the full directory), returned in displayed order, and carry league IDs reusable in odds/futures calls. It stops short of richer detail like rate limits or caching.

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, zero filler, with the core purpose front-loaded before the sibling routing. Every clause earns its place by either defining scope or directing alternatives.

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?

An output schema exists, so return values need not be described. The description fully covers what the tool returns, its ordering, and how it relates to sibling league/odds/futures tools, leaving no gap for an agent deciding whether to call it.

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 no parameter surface to document; baseline 4 applies. The description adds no parameter guidance because none is needed.

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 verb ('List'), a precisely scoped resource ('current home-page league shortcuts'), and the return characteristic ('in displayed order, with league IDs'). It also names the sibling tools it is not, so an agent can distinguish it from draftkings_leagues and draftkings_featured_leagues without opening any schema.

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?

Explicitly routes the agent: 'Use draftkings_featured_leagues for featured flags or draftkings_leagues for the full sports and league directory,' giving both alternatives and the condition that selects each. It further notes the returned IDs work with odds and futures, clarifying downstream usage.

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