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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds return-shape context that the annotations cannot: it discloses that the result aggregates every chain deployment plus total TVL and a curated description. It says nothing about behavior for an unknown or ambiguous symbol, which is the remaining gap.

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?

A single sentence that front-loads the verb and scope and then lists the returned fields; every clause earns its place and there is no padding.

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 one-parameter read tool with full annotation coverage, the description is nearly complete - it covers scope, key parameter semantics and return contents in the absence of an output schema. Only the failure mode for an unrecognized symbol is unaddressed.

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% and the schema already defines 'symbol' with an example, so the baseline is 3. The description adds matching examples (BUIDL, USDY, OUSG) that confirm the expected symbol vocabulary, but no format or case-sensitivity rules.

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 gives a specific verb and resource ('Returns every deployment of one tokenized asset symbol ... across chains') plus the concrete payload (TVL, curated description), so the agent knows exactly what it gets. It stops short of naming any sibling (e.g. get_tokenized_equity or list_rwa_yields) to confirm this is the single-symbol, cross-chain lookup rather than a list endpoint.

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 when-to-use or when-not-to-use guidance and no alternative is named, even though siblings such as get_tokenized_equity, list_rwa_yields and rwa_issuer_terms occupy adjacent territory. The agent must infer from the name alone that this is the single-symbol lookup.

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