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

With no annotations, the description carries the full burden, and it does disclose real behavior: a $0.005 USDC toll via x402 and, critically, that the tool returns 402 payment instructions instead of data when payment fails. It stops short of describing return shape, freshness, or rate limits beyond price.

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 tight, front-loaded sentences: identity/purpose first, cost second, fallback third. The 'Mini's TrollBridge' branding is slight fluff but functions as identity, and nothing is redundant.

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 one-optional-param list tool with no output schema and no annotations, the key unknowns — cost and the 402 failure path — are covered. Only the returned record shape and data freshness are unaddressed, which is a minor gap given the purpose sentence already sketches the payload.

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% for the single optional limit parameter (range and default already documented). The description only restates 'limit 1-200', adding no pagination or ordering semantics beyond the schema, so the baseline of 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?

States a specific resource (upcoming class-action and claim deadlines) with a clarifying gloss ('money with an expiry date'), so an agent immediately knows it returns dated monetary claims. It does not name or contrast any sibling (bridge_bounties, bridge_sweepstakes), so it falls short of full differentiation.

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 description never says when to use this over the many adjacent tools (bridge_bounties, bridge_sweepstakes, bridge_opportunities). The only conditional it gives is the payment fallback, which is a failure mode rather than usage guidance.

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