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

With no annotations, the description carries the full burden and does disclose critical non-obvious behavior: it is a paid tool ($0.05 USDC via x402) and returns 402 payment instructions rather than data when payment fails. This is exactly the kind of behavior an agent must know before calling. Minor gap: no mention of result shape or latency.

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?

Front-loaded with the core purpose, then payment terms, then the parameter note. Every sentence carries information (what it scans, cost, failure mode, parameter bound) with no padding.

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 single-parameter read tool with no output schema, the description covers purpose, cost, and payment-failure behavior sufficiently to call it correctly. The unexplained 0-100 scoring methodology and result contents are the only mild gaps.

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 coverage is 100% and the single 'limit' parameter is fully documented in the schema, including default 50 and range 1-200. The description merely restates 'Optional limit 1-200', adding no meaning 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 verb+resource ('token rug scan') and enumerates what it evaluates: liquidity, holders, and a 0-100 safety score. An agent can tell it apart from the generic bridge_* siblings, though it does not explicitly name them.

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?

No guidance on when to prefer this over alternatives (e.g. bridge_fresh, bridge_new_pairs, bridge_search). The only conditional guidance is payment-related ('If you cannot pay... returns 402'), not task-selection guidance.

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