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 well: it discloses a per-call cost ($0.05 USDC on Base or Solana via x402) and the failure mode (returns 402 payment instructions instead of data). It stops short of describing result shape, ordering, or rate limits.

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?

Roughly three dense sentences, front-loaded with the resource and payload, then payment terms, then parameters. The TrollBridge branding is mildly expendable but does not bloat the definition.

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 must carry return-value meaning; it does so at a high level (listings with rug scores). Combined with the payment and 402 behavior, an agent has enough to invoke it correctly, though pagination and exact result fields remain unspecified.

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% and both parameters are already documented with ranges and a default, so the schema does the heavy lifting. The description's 'Optional limit 1-50, chain' merely restates the schema and adds no format or semantics beyond it.

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 (newest token listings) plus the distinguishing payload (rug scores) and the workflow it serves (check-then-ape sniping). An agent can separate it from bridge_token_check or bridge_fresh, though it never names those siblings explicitly.

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 phrase 'for check-then-ape sniping' implies a use context, and the payment caveat tells the agent what happens on failure, but there is no explicit when-to-use vs. when-not, nor any routing to bridge_token_check or bridge_fresh for related checks.

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