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

Annotations already declare read-only, non-destructive, non-idempotent behavior; the description adds the crucial nuance that results are random on each call unless seed_text is supplied, in which case the same text yields the same numbers for the whole UTC day. It also discloses that seed_text is not stored and instructs the agent to surface the note field, both real behavioral context rather than restating annotations.

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 presets are front-loaded in the first sentence and the whole thing is three tight sentences. The entertainment disclaimer is slightly redundant ('predicts nothing', 'same odds', 'no pick improves the chance' all say the same thing), which keeps it from a 5.

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 small read-only generator with a full schema, complete parameter descriptions, an output schema, and honesty annotations, the description covers the remaining agent-relevant gaps: mode selection, seeding behavior, non-persistence of the seed, and the need to surface the note field.

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?

Schema description coverage is 100%, so every parameter including min/max/numbers/date/seed_text semantics is already documented. The description reinforces the custom-mode dependency and the seed_text/day relationship but adds little beyond what the schema states, so the baseline 3 applies.

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 ('random number picks') plus the exact preset families supported (powerball, mega_millions, euromillions, uk_lotto, custom) with their ball ranges. An agent knows precisely what it will get back: lottery-style draws or a custom-range draw.

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 operational context: use presets or custom, give seed_text for a stable daily set, and it explicitly frames the tool as entertainment-only that 'predicts nothing' — a strong cue that it should not be invoked for real forecasting. It stops short of explicit exclusion conditions or routing to alternatives (there are no siblings), so not quite a 5.

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