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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld), so the description's main contribution is the pay-per-call model: $0.08 USDC per call and payment headers (X-Payment / X-Payment-Tx / Bearer fg_…) supplied in MCP headers rather than parameters. That is genuinely useful behavioral context, but nothing is said about response shape, pagination, failure/refund behavior, 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?

The purpose statement is front-loaded and useful, but the content is duplicated across Chinese and English blocks, '参数同左' is meaningless without hidden context, and the bilingual restatement adds length without adding information.

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 3-parameter tool with no output schema, the description does sketch the returned metrics and covers the important auth/billing mechanics. However, it leaves parameter semantics and the exact ranking/sorting behavior unexplained, which is a notable gap given zero schema coverage.

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, yet it only lists the names 'chain, top, sort' with no meaning, format, defaults, or examples (e.g. what values 'sort' accepts, whether 'top' is a count or a threshold). The 3 parameters remain effectively undocumented.

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 states a specific verb+resource (bridge flow ranking) and enumerates the returned content: per-bridge volume tiers, market share, 1d/7d WoW, chain coverage and chain count. The word 'full' / '完整排行' hints it is the complete ranking rather than a snapshot, but it never names bridge_now or any sibling to make the distinction explicit.

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?

There is no statement of when to choose this over bridge_now or quote_compare; the only usage-adjacent phrase is the cryptic '参数同左' (args as on the left), which references context an agent does not have. No prerequisites, no exclusions.

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