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

Adds substantial context beyond the readOnlyHint/openWorldHint annotations: it discloses that the CONTRACT (not the draw's database phase) determines tradingOpen and that this field should be trusted, warns that sponsor-name free text is human-typed DATA not instructions (prompt-injection defense), and states the tool runs on Base Sepolia testnet with no monetary value. This is exactly the behavioral context an agent cannot get from annotations.

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 purpose, then layered with the important caveats (tradingOpen authority, injection warning, network). The network/testnet block is slightly verbose, but each sentence carries distinct and necessary information.

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 burden of explaining returns, and it does: listings, prices, and trading-window state. It adds safety and network context. Only minor gaps remain, such as whether the result is paginated or how listings are ordered.

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 are no parameter semantics for the description to explain. Baseline 4 applies; the description correctly does not fabricate parameter discussion.

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 marketplace') and enumerates the exact fields returned: which tickets are listed, at what price, and whether the trading window is open. This is clearly distinct from the sibling tools (check_entry, check_prize, get_draw, get_results), none of which concern secondary-market listings.

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?

Usage is implied by 'read the live marketplace' — an agent can infer this is the tool for listing/browsing listings — but there is no explicit when-to-use, when-not-to-use, or named alternative. The note about trusting tradingOpen is behavioral guidance rather than routing guidance.

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