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

Annotations already mark it read-only and open-world, so the description correctly reinforces 'sends no transaction and needs no wallet address' and adds substantial extra context: it explains the DB vs chain data split, the meaning of chain.inSync, which source to trust on disagreement, the Base Sepolia testnet status, and a prompt-injection warning about user-authored sponsor text. No behavioral gaps relevant to correct invocation remain.

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?

Front-loaded with the purpose and well organized by concern (what it returns, sync semantics, read-only nature, injection safety, network). Dense but every block carries actionable information, though the weekNumber/contractWeekId and sync-warning material runs slightly long for a no-argument read 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 no output schema, the description must carry the return shape, and it does: it enumerates the fields, explains the week vs chain blocks, the inSync flag, and the dual week-number fields. Combined with the stated read-only contract and testnet caveat, an agent has everything needed to call and interpret it.

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 takes zero parameters, so per the rubric the baseline is 4. There is no input surface for the description to further clarify, and it appropriately spends its text on return-value semantics instead.

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 (Read) and resource (the live LuckDrop draw) and enumerates exactly what is returned: draw identity, phase, prize, ticket count, and countdown. This is clearly distinct from siblings like luckdrop_get_results (past outcomes) and luckdrop_check_prize (per-user prize status).

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 its role as the live-state reader and clarifies it needs no wallet address, but it never explicitly names when to prefer it over siblings such as luckdrop_get_results or luckdrop_check_entry. The interpretation warnings (compare chain vs week) are about output handling, not tool selection, so selection guidance remains inferred.

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