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

Annotations already declare readOnlyHint=true and openWorldHint=false, and the description goes beyond them by disclosing the shape of the payload (chain-by-chain contracts, issuer provenance, signature verification outcome). It doesn't say what happens for an unknown id or whether the call is metered, which keeps it from a 5.

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 fragment that enumerates the returned content with no filler. It is dense but every clause maps to a real payload component; only the somewhat compressed phrasing keeps it from a 5.

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 must carry the return-value burden, and it does so by listing the four content areas an agent will receive. Missing only lookup-failure behavior and any note about cost or side data, so it is nearly complete for a simple read-by-id 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 coverage is 100% with a full enum of ~80 allowed ids, so the schema already carries the semantics; the description's 'entry id, from list_tokenized_assets' merely restates it. Baseline 3 is appropriate, with no added format or edge-case guidance.

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?

Names the resource ('One Asset Map entry') and enumerates exactly what it contains: the security, per-chain token contracts, issuer sources, and IoMarkets signature verification status. That is far more specific than a tautology, though it never explicitly contrasts itself with list_tokenized_assets or verify_asset_with_issuer.

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: the id parameter says 'from list_tokenized_assets,' so an agent can infer this is the detail-fetch following the list call. There is no explicit when-to-use/when-not statement and no pointer to alternatives such as verify_asset_with_issuer for signature questions.

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