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

The annotations only declare readOnlyHint and openWorldHint, so they say nothing about scope limits. The description adds the substantive caveats an agent needs: reachability is unverified, the snapshot implies no local availability, and it returns no picks or projections.

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?

Purpose and the counts come first, then the usage hint, then the caveats, so it is well front-loaded. The middle clause ("product-page reachability is not verified") interrupts the main flow slightly and makes it more densely packed than necessary.

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?

Output schema exists, so return-value detail isn't needed, and the description covers scope, freshness ("dated snapshot"), and the sibling boundary. It does not say how often the snapshot is refreshed or what the jurisdiction note actually contains.

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 no parameters, so the baseline is 4. The description's only parameter-like information is what the snapshot contains (14 categories, 21 links), which is output content rather than input semantics.

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 names a specific verb and resource: a dated public Help Center snapshot of DraftKings Pick6 sports and formats, with counts (14 categories, 21 links) and exact sport codes. It is clearly distinguishable from draftkings_pick6_rules and draftkings_pick6_rule_page, which it cites for scoring detail.

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?

It states directly what the tool is for ("Use it to discover advertised formats") and routes adjacent needs to a named sibling ("Use draftkings_pick6_rules for scoring details"). It also states what the snapshot does NOT establish: product-page reachability and local availability.

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