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

The description goes well beyond the annotations by disclosing the paid nature ($0.01 per call, USDC on Solana), the exact two-step x402 handshake, and an HTTP fallback endpoint. That is behaviorally important context no structured field carries. It stops short of describing the response shape or whether scores are cached/live, which keeps it off a 5.

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 sentences that front-load the purpose and then pack payment mechanics without filler. The parenthetical payment instruction is dense but earns its place; it could be split for readability but nothing is wasted.

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 5-parameter, zero-required, free-form scoring tool with no output schema, the payment path is fully covered but the inputs are not - an agent still doesn't know what a valid call looks like or what it gets back. Adequate on the monetization dimension, incomplete on the data dimension.

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?

Though coverage is nominally 100%, every schema description is a vacuous type echo ("string", "number"), so the schema conveys nothing. The description names no parameters at all - token, bridge, from_chain, to_chain, and amount_usd are never explained, and the reader cannot tell whether 'token' is an asset symbol, a bridge token, or a payment token.

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 opening sentence states a specific verb and resource plus the scoring dimensions: "Score a bridge by security, liquidity, and incidents." It is clear in isolation, but it never distinguishes itself from nearby siblings such as tokens_score, batch_score, or fee_oracle_recipe, so the agent must infer the boundary itself.

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 gives strong *how-to-invoke* guidance (call without payment to receive the PaymentRequired challenge, then retry with payment at _meta["x402/payment"]), which is real usage context. It gives no *when-to-use* guidance, though: nothing says when to prefer this over tokens_score or batch_score, or which bridge/chain combinations are valid.

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