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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds real value by disclosing tier-gating: large transfers of the last hour, supply history and regulation items require the Tokenized Assets pass, Builder, Scale or PRO — behavior an agent cannot see in the annotations.

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 is front-loaded, but the long parenthetical ticker lists ('USDT, USDC, USD1, PYUSD, RLUSD...', 'BUIDL, Ondo...') consume significant space for marginal selection value, making it a dense wall of text rather than a tight definition.

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 carries the burden of describing returns, and it does so reasonably by listing the fields and the tier-dependent extras. It stops short of return format/pagination details, but for a single-optional-param read tool it is largely complete.

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%, so the token id is documented. The description adds genuinely useful semantics beyond the schema: the range of valid asset categories and, crucially, the behavior of the optional parameter when omitted ('the list'), which the schema does not state.

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 clearly states the resource — a per-token hub that reads tokenised-asset data from contracts — and enumerates the covered asset classes and returned fields (price, supply, value, 24h change, issuer, contract). It does not, however, name the closest siblings (get_tokenization_overview, get_carv, get_stablecoin_net_mint) to differentiate itself, so an agent must infer the boundary.

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?

Usage is only implied: 'No token given: the list' tells the agent what happens with an empty call, and the tier mentions hint at gated data. There is no explicit when-to-use / when-not-to-use guidance versus the related tokenization and CARV tools.

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