draftkings_quick_links

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

With no annotations provided, the description carries the full burden. It clearly states the return is ordered and reflects current home page prioritization, which conveys the dynamic nature and the ordering guarantee. It doesn't disclose pagination or any potential empty result behavior, but for a zero-parameter tool this is acceptable.

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 that are entirely value-dense; the first clearly states the resource and ordering semantics, the second explains the league_id's usefulness for downstream calls. No filler or redundancy.

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 zero-parameter list tool, the description covers purpose, scope, ordering, and downstream use of the returned league IDs. The absence of an output schema is partially compensated by the description's mention of a numeric league_id per item. It doesn't list other fields in items, which is a mild gap, but not critical for selection.

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 has no parameters, so schema coverage is effectively 100%. The description doesn't need to explain parameters since there are none. The baseline of 4 for zero-parameter tools applies, and the description's mention of the output shape gets the semantics to a solid level.

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 'Returns the ordered league shortcuts currently prioritized on DraftKings Sportsbook's public home page' with a specific verb and resource. This distinguishes it from sibling tools like draftkings_odds or draftkings_futures by explaining it returns navigation shortcuts, not betting data.

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 implicitly signals when to use this tool: when you need the current prioritized league shortcuts from the home page. It doesn't explicitly mention alternatives, but the clarity of the resource makes the use case evident. The included note that each league_id is accepted by /draftkings/sportsbook/odds and /draftkings/sportsbook/futures adds practical downstream routing guidance.

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