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

Annotations already establish readOnly and openWorld, so the description focuses on what to expect: it returns only two specific sections, omits others, and is informational rather than gambling advice. This is genuinely useful scoping context beyond the annotations, though it doesn't describe output shape or size.

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?

Four short sentences, front-loaded with the what, followed by when-to-use, exclusions, and a disclaimer. Each sentence adds information; nothing is redundant, though the closing disclaimer sentence is slightly tangential.

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 zero params, an output schema present, and annotations covering safety, this description covers everything needed to select and invoke it: what content comes back, what doesn't, and the informational nature. Only the lack of explicit sibling routing keeps it from a 5.

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?

Zero input parameters, so there is nothing to document and the baseline of 4 applies. The description correctly conveys that the call is parameterless in effect by describing a fixed-content fetch.

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 resource (DraftKings slots guide) with the exact scope of sections returned (basic rules, responsible-play). It identifies itself as the slots guide, implicitly distinct from the DFS glossary/guide siblings, but never names those siblings to make the distinction explicit.

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?

Gives clear triggering conditions: 'use this when you need official slot terminology or a responsible-play reference,' and clarifies the excluded sections (account setup, payment, promotion, strategy). It doesn't point to an alternative tool for those excluded topics, so a small routing gap remains.

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