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

With no annotations supplied, the description carries the full burden and does well: it states the data is read live from chain (implying a read-only, non-mutating call) and discloses the nontrivial return behavior that price is null when no pool exists rather than a synthesised home-chain value. It does not cover pagination, result caps, or whether an omitted symbol returns all bridged assets, so it is not exhaustive.

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 scope and return fields are front-loaded, and each sentence adds information rather than restating the title. The final sentence is slightly padded ("a number you cannot actually get"), but the substance justifies the length.

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 and no annotations, the description competently substitutes by enumerating return fields and flagging the null-price case. The remaining gap is the no-filter default behavior and result-set size, which matters for a listing-style tool.

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% for the single optional symbol parameter, so the baseline applies. The description adds modest value by illustrating the naming convention ((WSOL.X), (USDC.X)), but does not say whether the filter is exact-match or partial, nor what happens by default when it is omitted.

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 specific resource and scope: assets bridged onto X1 (WSOL.X, USDC.X) read live from chain, and enumerates the fields returned (supply, holder count, top-holder concentration, token program, mint/freeze authority, pool existence). That scope is distinctive versus siblings like token_lookup or arc_token_check, though no sibling is named explicitly to sharpen the distinction.

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?

"An asset can be genuinely live on X1 and still have no market — this tells those apart" gives a concrete use case that selects this tool over a plain token-info lookup. There is no explicit when-not-to-use clause or named alternative, which keeps it short of a 5.

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