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 genuinely new behavior by disclosing that only links with 'verified REST support' are returned and that 'unverified upstream links are omitted'. The explicit exclusion list further sets expectations about result contents. It stops short of noting volatility or caching of upstream rule pages.

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 tight sentences, front-loaded with what is fetched, followed by the follow-up instruction and then the negative scope. No restatement of the tool name and no filler.

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 need not enumerate return fields, and it still flags the slug field that matters for chaining. For a zero-parameter read tool, nothing an agent needs to invoke and follow up 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?

The tool takes zero parameters, so the baseline is 4 and there is nothing for the description to disambiguate on the input side. The mention of 'returned slugs' usefully previews the output field that feeds the sibling tool, but that is return-value context rather than parameter 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?

States a specific verb ('Fetch') and a precisely scoped resource ('public DraftKings Pick6 Rules and Scoring sections and links for detail pages'), then names the sibling draftkings_pick6_rule_page as the downstream consumer. An agent can distinguish it from draftkings_pick6_rule_page without opening either 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 instructs 'Use the returned slugs with draftkings_pick6_rule_page', giving a clear call sequence, and the negative clause ('does not return picks, projections, entries, or geolocation tokens') rules out misuse. It does not distinguish itself from the nearby sibling draftkings_dfs_rules_and_scoring, which is the one remaining ambiguity.

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