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

With no annotations, the description carries the full behavioral burden and does a good job: it discloses the per-call cost ($0.02 USDC), the payment rails (Base or Solana via x402), and the failure mode (returns 402 payment instructions instead of data). It omits what a successful response actually contains and whether it is a safe read, which are minor residual gaps.

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?

Three short, front-loaded sentences with no filler; the paying behavior and failure mode are stated crisply. The brand preamble ('Mini's TrollBridge') is slightly wasteful but does not obscure the payload.

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?

For a tolled tool with no output schema and one fully documented parameter, the description covers the essentials an agent needs: cost, payment method, and the 402 fallback. It stops short of describing the returned payload shape, but no output schema exists to offload that to.

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%, so the schema already fully documents the single optional 'limit' parameter with its 1-200 range and default of 50. The description merely restates 'Optional limit 1-200', adding no meaning beyond the schema — 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?

The description names a distinct resource ('free-to-enter sweepstakes with real prizes') that no sibling covers, so an agent can tell it apart from bridge_bounties, bridge_yields, etc. However, the operation itself is only implied by the 'Optional limit 1-200' clause — there is no explicit 'list/return sweepstakes' verb, and the branded 'Mini's TrollBridge' framing adds noise rather than clarity.

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?

There is no guidance on when to call this tool versus the many bridge_* siblings, nor prerequisites beyond the payment requirement. The description only states operational mechanics (toll, failure behavior), not usage context or alternatives.

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