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

Annotations already declare readOnly, idempotent and non-open-world, so the safety profile is covered. The description adds genuine context beyond that: the data comes from the site's calendar, covers both regular and special draw dates, and explicitly excludes recommendations/forecasts, which guards against misuse.

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 tight sentence that front-loads the resource and its contents. The trailing 'official results only; no forecasts' clause is a useful scope guard rather than filler, though it slightly dilutes the otherwise clean return-value statement.

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?

For a no-parameter read tool with no output schema, the description adequately conveys what comes back (draw dates plus operators). Nothing critical is missing, though it does not mention format, time horizon covered, or ordering, which would fully close the loop.

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 for the description to document; the baseline for a parameterless tool is 4. The description correctly implies no input is needed to retrieve the schedule.

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 and resource: returns the official upcoming 4D draw schedule with regular/special dates and the operators drawing on each date. It is clearly about the schedule rather than results, so an agent can separate it from the results-oriented siblings, though no sibling is named explicitly.

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 the 'upcoming schedule' scope and the 'official results only; no number recommendations or forecasts' disclaimer, which tells the agent this is not a prediction tool. However, it never states when to prefer this over get_latest_results or get_results_by_date, leaving the routing to inference.

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