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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is clear. The description adds little behavioral context beyond noting prize tiers and bonus configuration; it does not state assumptions such as fair draws or whether multiple tickets/combinations are handled.

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?

The purpose is front-loaded and the description is reasonably short. Some sentences are redundant or low-value: the return-value sentence duplicates the output schema, and the list_bundles cross-reference is not needed for invoking this tool.

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 a full input schema, an output schema, and rich annotations, the description supplies enough context to identify and call the tool correctly. It is slightly incomplete on usage routing among the many probability calculators, but that is a minor gap for a deterministic calculator.

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 the schema already documents all four parameters. The description merely lists the same inputs at a high level ('numbers to pick, total numbers, bonus number config') without adding format, constraints, or examples beyond the schema.

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 ('Compute') and resource ('odds of winning a lottery') and scopes it to prize tiers. It is distinguishable from generic probability siblings by the lottery focus, but it does not explicitly differentiate itself from the other probability calculators in the sibling list.

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?

The only usage text is 'Use for awareness, education,' which is vague and does not explain when to choose this over calculate_card_draw_probability, calculate_dice_probability, or other probability tools. No exclusions or alternative-routing guidance is provided.

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