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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the tool is known to be a safe read with external dependencies. The description adds vital behavioral context: the two id spaces can yield the same number for different draws, and the response echoes the space used plus both ids. It also discloses that the tool operates on Base Sepolia, a test network with no monetary value. This is excellent transparency beyond 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?

The description is front-loaded with the core purpose, then follows with important parameter context and network warning. It is well-structured and each sentence serves a purpose. Slightly verbose in the network warning, but the information is necessary for safe use.

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?

Given no output schema, the description adequately clarifies the return: it echoes the id space and both ids. It also covers the network context. The main missing element is an explicit note about the return format for the rounds and winner, but that is partially implied. Overall, it is complete enough for correct invocation.

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 coverage is 100%, so the schema provides basic definitions. However, the description adds significant meaning beyond the schema: it clarifies that `week` is the DISPLAY week number by default and that the same number in contract space refers to a different draw. This is critical semantic information not captured by the schema's generic 'draw number' description.

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: read a single draw's five rounds and its winner. It is clearly distinct from sibling tools like luckdrop_get_draw, which likely covers a broader or different draw context. The description is clear but does not explicitly differentiate itself from that sibling.

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?

Provides crucial usage context: it explains that `week` defaults to display numbering and warns to use idSpace='contract' when following contractWeekId. This tells the agent exactly when and how to use the parameter to get the correct draw. It does not mention when to prefer this tool over siblings, but the context is strong for correct invocation.

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