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

With no annotations, the description carries the behavioral burden and does so unusually well: it discloses the $0.05 USDC toll, the Base/Solana rails via x402, and the critical fact that an unpaid call returns 402 payment instructions instead of data. Gaps remain around rate limits, caching/freshness of odds, and failure modes beyond non-payment.

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?

The key facts (what it returns, its cost, its failure behavior) are front-loaded into three compact clauses with no wasted sentences. Minor inflation comes from branding ('Mini's TrollBridge') and the redundant parameter restatement at the end.

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 two-parameter tool with no output schema, the description adequately characterizes the return payload ('live Polymarket odds, prices, and volume') and explains the non-obvious tolling/payment contract. Only the absence of freshness or rate-limit context keeps it short of fully complete.

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 both parameters are already fully documented with examples and defaults in the schema. The description's 'Requires q; optional limit 1-25' merely restates the schema without adding syntax or search-semantics guidance, so 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 specific domain verb+resource: prediction-market intel, live Polymarket odds, prices, and volume. That domain framing distinguishes it from generic siblings like bridge_prices or bridge_search, though no sibling is named explicitly. The brand preamble ('Mini's TrollBridge') and 'agent-ready JSON' are filler rather than purpose.

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 explicit guidance on when to choose this tool versus alternatives such as bridge_prices or bridge_search; usage is only implied by the 'prediction markets' framing. The one strong usage-adjacent signal is the payment condition and its fallback, which tells the agent when the call will fail rather than when to use it.

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