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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds useful context that the data comes 'from the site's calendar' and is official-only, but says nothing about freshness, caching, or whether the schedule is refreshed.

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?

One front-loaded sentence names the resource and its contents, with the disclaimer tacked on to bound scope. No wasted phrasing, though the closing disclaimer is more of a general site policy than tool-specific guidance.

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 no parameters and no output schema, the description carries the burden of describing the return shape, and it does so ('regular and special draw dates' plus operators per date). For a simple read-only lookup this is sufficient; only freshness/refresh behavior 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 there is nothing to document and the baseline of 4 applies. The description correctly does not invent parameter detail.

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 states a specific verb and resource ('Returns the official upcoming 4D draw schedule') and enumerates the payload (regular/special draw dates plus which operators draw on each date). This is clearly distinct from the results-oriented siblings, though it never names a sibling to route against.

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?

Usage is implied by 'upcoming draw schedule' and the disclaimer 'Official results only; no number recommendations or forecasts,' which sets a scope boundary. However, there is no explicit when-to-use versus the sibling results tools, nor any prerequisites or exclusions beyond the forecast caveat.

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