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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds real value beyond that by disclosing the free tier with a daily per-caller quota and the crucial operational detail that payment credentials (X-Payment, X-Payment-Tx, Bearer fg_…) belong in HTTP headers, not in tool arguments. It does not describe the shape or size of the returned payload, but with annotations carrying the safety burden a 3 is warranted for a free snapshot tool.

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 core purpose is front-loaded, but the text is then repeated three times: a bilingual opening line, a full [zh] block, and a full [en] block that re-lists the same arguments and quota. The mixed Chinese/English inline phrasing plus duplicated sections add length without adding information, so most sentences do not earn their place.

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?

With no output schema, the description does a reasonable job of telling the agent what comes back (volume across three windows, top-3 share and detail) and how payment is authenticated. What is missing for a zero-required-parameter, zero-coverage schema is any explanation of the filters, and there is no mention of quota-exhaustion behavior or pagination/limits on the returned bridge list.

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 0%, so the description carries the full burden for three parameters. It only restates the names 'chain / top / sort' and says they are optional, which the schema already conveys via default null and zero required fields. Nothing explains what 'top' means numerically, what values 'sort' accepts, or what chain identifiers are valid, so it fails to compensate for the coverage gap.

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 concrete resource and scope: whole-market cross-chain bridge volume over 24h/7d/30d plus top-3 bridge share and detail. That is enough for an agent to know this is a market-wide bridge flow snapshot rather than a per-bridge lookup. It stops short of naming or contrasting with the sibling bridge_ranking, so differentiation is left to inference.

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 framing question 'where is bridge money flowing' hints at intent, and the free daily quota is stated, but there is no explicit when-to-use / when-not-to-use guidance and no routing to alternatives such as bridge_ranking or bridge_quote. The agent must guess whether this or the ranking sibling answers a given question.

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