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

Annotations already state readOnlyHint=true and openWorldHint=true, so the description's only addition is that it returns metadata fields. It does not disclose freshness, update cadence, or what happens on a missing/invalid event_id, so it adds little beyond the annotation surface.

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?

A single short parenthetical sentence, front-loaded with the resource and its returned fields. Efficient, with no waste, though it forgoes the space where usage and parameter guidance should live.

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 needn't be explained, but with a 0%-coverage required parameter, numerous sibling tools, and no usage routing, the description is insufficient to call the tool correctly.

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 description coverage is 0% and the sole required parameter (event_id) is undocumented anywhere. The description names no parameter and gives no format hint (numeric vs. slug) for event_id, leaving the agent to guess.

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 resource ('DraftKings Sportsbook event metadata') with the fields it returns (teams, status, start time), so the agent knows it fetches a single event's metadata. It is clear but does not distinguish itself from sibling draftkings_event_context or draftkings_event_markets.

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?

No when-to-use or when-not-to-use guidance, and no mention of alternatives such as draftkings_event_context or draftkings_event_markets exists in the description. The agent must infer the route from the name alone.

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