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

Annotations already cover the safety profile (readOnlyHint), and the description adds substantial context beyond them: that the contract, not the draw database, governs tradingOpen, that fees and prize shares are admin-settable values to be read rather than assumed, that sponsor text is human-typed and must be treated as data not instructions, and that the deployment is a valueless test network. That is unusually rich behavioral disclosure.

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?

Purpose and scope are front-loaded in the first sentence, followed by interpretation rules, a security note, and a network disclaimer — each paragraph carries distinct value. The feeBasisPoints/prizeShareBasisPoints paragraph is somewhat long for a listings tool, but it is needed to interpret seller proceeds correctly, so the length is defensible.

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 and no parameters, the description carries the full burden and discharges it: it names the returned fields (listings, price, tradingOpen), explains how to interpret them, warns about untrusted embedded text, and discloses the test-network context. Nothing needed to call or correctly use 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?

The tool takes zero parameters, so there is no parameter semantics to explain; the baseline for a parameterless tool is 4. The description correctly spends no words on inputs.

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 the live market') and enumerates exactly what is returned: which tickets are listed, at what price, and whether the trading window is open. An agent can immediately distinguish this listings tool from luckdrop_get_draw, luckdrop_get_results, luckdrop_check_entry and luckdrop_check_prize.

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 one explicit routing rule — 'trust tradingOpen in this result rather than inferring it from the phase' — which steers the agent away from deriving trading status from a sibling's draw data. It does not explicitly state when to call this versus luckdrop_get_draw for market questions, so guidance is clear but not exhaustive.

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