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

Adds substantial context beyond the readOnly/openWorld annotations: the answer comes from the chain not a database, the return is an UNSIGNED tx, the service never signs or holds keys, the mined tx is irreversible, entry itself is free and the entrant pays only gas, and the whole thing runs on Base Sepolia testnet with valueless LUCK. That is exactly the behavioral disclosure an agent needs before gating a transaction.

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: the core question is answered in the first sentence, then return shape, signing model, and network follow in descending order of importance. The testnet warning is somewhat emphatic and repeated in tone, but every block earns its place for a tool gating irreversible transactions.

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?

There is no output schema, so the description carries the return-value burden and does so fully: canEnter, a reason mirroring the contract's revert strings, and the exact unsigned transaction. Combined with the signing and network caveats, nothing needed to call or act on the result is missing.

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 description coverage is 100%; the single address parameter is fully documented with pattern and network in the schema. The description adds no syntax or format detail beyond what the schema already states, so the baseline 3 applies.

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?

Opens with a precise framing of the operation: eligibility for the current draw plus the exact transaction payload. That is a specific verb+resource, and its scope is genuinely distinct from siblings like luckdrop_check_prize or luckdrop_get_results. It stops short of 5 because it never names or contrasts a sibling, leaving the differentiation to inference.

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?

Gives an explicit trigger: "Call this before sending an entry, every time," and explains why it must be fresh (sourced from the chain, a stale yes costs gas on revert). It never states when NOT to call it or point to an alternative, so it falls short of the 5 bar.

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