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

readOnlyHint=true already declares the safety profile, so the description only needs to add context beyond that. 'Canonical' is a genuinely useful disclosure that results are normalized/authoritative rather than raw, but nothing is said about behavior for unknown addresses or non-canonical tokens. An output schema exists, so return-shape detail is rightly omitted.

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 front-loaded sentence with zero filler, and the scope qualifier arrives before any implied detail. It is arguably too terse to route the agent against the many token-related siblings, but nothing in it is wasteful.

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 two-required-parameter read tool with full schema coverage, annotations, and an output schema, the definition covers what is needed to call it correctly. The only shortfall is the missing disambiguation from get_tokens and list_tokens in a crowded sibling set.

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 both chain_id and address are already documented, making 3 the baseline. The word 'exact' hints that matching is strict with no fuzzy/symbol resolution, but the description adds no format or type guidance beyond the schema.

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?

States a specific verb ('Fetch') and resource ('canonical token metadata') scoped to an exact chain and address, which implicitly separates it from the plural siblings get_tokens/list_tokens/export_tokens. It stops short of naming an alternative, so an agent must infer the singular-vs-list split.

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 phrase 'for an exact chain and address' implies this is the single-token lookup path, giving implied usage context. There is no explicit when-to-use/when-not or named alternative such as get_tokens for batch or list_tokens for discovery.

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