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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety and external-dependency are covered. The description usefully adds that it fetches live third-party sources and verifies *every* listed contract (all-or-nothing scope). It does not say what happens when a contract is missing, an issuer source is unreachable, or how expensive/slow the live check is.

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 dense sentence, front-loaded with the action and the sources, closing with the rationale for using it. No filler or restatement of the name.

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?

The mutation/safety profile is covered by annotations and the parameter set is trivial, but there is no output schema, and the description never indicates what a result looks like (per-contract booleans, a list of missing contracts, an error on unreachable source). For a live verification tool, that omission meaningfully limits correct interpretation of the response.

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?

Only one parameter, with 100% schema coverage and a self-describing enum of entry ids, so the schema carries the load. The description adds that the id refers to a single Asset Map entry, but nothing beyond that (e.g., whether ids are ticker-like slugs or opaque keys). Baseline 3 applies.

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?

Specific verb ('Fetch ... and confirm') plus resource ('the issuer's own sources for one Asset Map entry'), and it names the concrete source types (contracts page, public API, stellar.toml). It does not distinguish itself from the nearby sibling check_token_contract or get_tokenized_asset, so an agent gets no explicit routing signal between them.

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 clause 'so trust needn't rest on IoMarkets' implies the usage context: you call this when you want independent, first-party confirmation rather than a platform-sourced answer. There is no explicit when-to-use/when-not or named alternative (e.g., vs. check_token_contract), so the routing is left to inference.

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