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

Rich disclosure beyond the annotations: returns an unsigned {to, data, value} transaction, never signs or holds keys, requires user approval on Base Sepolia, is irreversible once mined, and is on a test network with valueless LUCK coins. The 180-day claim window and the 26-week scan window are also surfaced. The only minor gap is it does not say explicitly whether a no-prize result is an empty response or an error.

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 core action, then clearly delimited SCOPE and NETWORK sections that each carry necessary constraints. It runs long and repeats the unsigned-transaction point once, but nearly every sentence prevents a concrete misuse, so the length is largely justified.

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 compensates by describing the return shape ({to, data, value}) and the fact it is unsigned. Combined with scope limits, week semantics, and the test-network caveat, an agent has everything needed to call and interpret this 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?

Schema coverage is 100%, so the baseline is 3, but the description genuinely enriches weekId: it is a CONTRACT week id that overrides the scan, reaches older weeks only on this deployment's escrows, and is the same id luckdrop_get_results reports. That context is not derivable from the schema's min/max bounds alone.

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+resource+outcome: checking whether a wallet has an uncollected prize and returning the transaction that claims it. It also clarifies the mechanism (read from chain, works without website sign-in), which separates it from luckdrop_check_entry and luckdrop_get_results, which deal with entries and results rather than claimable prizes.

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?

Explicit when/when-not guidance: default behavior scans the most recent 26 contract weeks, and passing an explicit weekId is prescribed for reaching older weeks on the same escrows. It also states the hard boundary that prizes in earlier deployments are unreachable and names luckdrop_get_results as the source of the contract week id.

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