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

No annotations are provided, so the description carries the burden of behavioral disclosure. It discloses what information is returned (current draw, ticket price, pot, ticket count, draw time), which is useful. However, it does not state whether this is a read-only operation, whether it reflects live state, or whether any side effects occur. The description is adequate but not rich in behavioral context.

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 description is a single sentence that front-loads the key information: current draw, ticket price, pot, ticket count, and draw time. It is concise and every phrase earns its place. It could be slightly more structured, but it is efficient and readable.

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 zero-parameter, no-output-schema tool, the description covers the main return values. However, it does not mention whether the data is live, cached, or how frequently it updates, nor does it clarify the currency or formatting of the pot and ticket price. Given the tool's simplicity, the description is mostly complete but leaves minor gaps.

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 has zero parameters, so the description need not explain parameter semantics. The baseline for zero-parameter tools is 4, and the description appropriately focuses on what the tool returns rather than parameters. No parameter information is missing.

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: it lists the current lottery draw, ticket price, pot, ticket count, and draw time. It is clear what the tool does, though it does not explicitly distinguish itself from sibling lottery tools like lottery_buy_how_to. The verb 'list' is implied rather than stated, but the resource and scope are clear.

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 description implies this is a read-only status/info tool for the lottery, and the sibling lottery_buy_how_to suggests an alternative for buying. However, it does not explicitly state when to use this tool versus alternatives, nor does it mention any exclusions or prerequisites. The context is clear enough for an agent to infer usage, but explicit guidance is missing.

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