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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds useful scope context — 'current public' events, availability tags, and the explicit exclusion of odds — but does not discuss pagination, freshness, or rate limits. Solid value beyond annotations without being exhaustive.

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?

Three sentences, zero filler, and the resource scope is front-loaded ahead of the retrieval hint and the sibling routing. 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?

With an output schema present the description needn't explain return values, and it still summarizes the returned fields. For a one-parameter read tool with full schema coverage and clear sibling routing, nothing an agent needs to call it correctly 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?

Schema coverage is 100%, so the single league_id parameter is already documented. The description adds material value over the schema by naming three sibling tools that supply the numeric league_id, which the bare schema field ('Numeric DraftKings league id') does not.

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) and resource (current public event records for a DraftKings league), and enumerates what the records contain (participants, IDs, times, status, availability tags). An agent can distinguish it from draftkings_event, draftkings_live, and draftkings_event_context without opening a 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 tells the agent where to obtain the required league_id (draftkings_leagues, draftkings_quick_links, draftkings_featured_leagues) and names the alternatives for adjacent needs (odds/details via draftkings_event, live scores via draftkings_live, navigation IDs via draftkings_event_context). When-to-use and when-not-to-use are both covered.

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