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

Beyond the readOnlyHint and openWorldHint annotations, the description discloses many behavioral details: it returns both weekNumber and contractWeekId, explains the database versus contract blocks, warns against comparing chain.state to week.status, states that no transaction or wallet is needed, and flags free text as data rather than instructions. It also notes the Base Sepolia test-network context and lack of monetary value.

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 and then layers in output semantics, safety guidance, and network context. It is longer than a typical zero-parameter tool, but most sentences earn their place; the brief 'This is a read' line is somewhat redundant with the readOnlyHint annotation.

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?

Despite having no output schema, the description thoroughly explains the important return blocks, their provenance, and how to interpret disagreements. Combined with the annotations and zero-parameter schema, an agent has everything needed to call and interpret this tool correctly.

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?

With zero parameters, the baseline is 4 according to the scoring rules. The description does not need to explain parameter semantics, and it correctly avoids inventing input details.

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 uses a specific verb ('Read') and resource ('the state of the live LuckDrop draw') and enumerates exactly which fields the draw state includes. It implicitly distinguishes itself from siblings like luckdrop_get_results by emphasizing the live/current draw rather than historical results.

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 when to use the tool by saying it reads the live draw state, but it never names alternatives or explicit when-not conditions. An agent can infer usage, but no routing guidance is provided for sibling tools such as luckdrop_get_results or luckdrop_check_prize.

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