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

Despite minimal annotations (only readOnlyHint=false, openWorld=true, idempotentHint=false, destructiveHint=false), the description adds substantial behavioral context: trades are public, the house never trades, nothing holds a key or moves money, and unsigned trades return sign_this/at/limit that must be signed locally via EIP-191 personal_sign. That is valuable beyond the annotations, though the economic mechanics (points payout, skins) are stated tersely.

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?

Information is front-loaded with the concept before the pipe-delimited `what` list, which is efficient, but the run-on structure and dense jargon make it harder to parse than it needs to be. Every element is relevant, but readability suffers.

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?

No output schema exists, so the description carries return-value burden, and it does not describe what season/market/board/wallet responses contain. The trade/signature flow is covered well, but the multiplexed nature of a 10-param tool with all-optional params leaves the agent guessing about defaults and required combinations.

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?

With 0% schema description coverage across 10 parameters, the description must compensate, and it largely does: it maps market/outcome/side/amount to quote and trade, explains side=buy|sell semantics for amount ('points to spend or shares to sell'), and clarifies the sign_this/at/limit/signature loop. The `wipe` parameter and `what` default are not explained, leaving a gap.

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?

The description conveys that this is a prediction-market tool ('Gates predictions: markets on how this wipe ends') and enumerates sub-operations via the `what` values (season, market, board, wallet, quote, trade). However, heavy in-domain jargon ('wipe', 'THE ISLAND', 'Millers or Thatchers', 'skins') obscures the concrete purpose, and it overlaps the sibling `trade` tool without clarifying the boundary.

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 `what` enumeration implies when to select each mode and the signature flow explains a required two-step for trades, but there is no explicit when-to-use guidance relative to siblings like `trade` or `prepare`, nor any statement of prerequisites beyond the 30-minute play note.

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