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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds a useful data-quality caveat ('ISIN where the issuer gives it'), but says nothing about result volume, pagination, or ordering for a collection endpoint.

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?

Two dense sentences with no filler: contents first, filtering second. Every clause carries information the agent needs.

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 annotations covering safety and no output schema, the description adequately conveys what comes back and how to narrow it. The remaining gap is collection behavior (pagination, result limits), which an agent would want before calling a list endpoint.

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?

The schema only labels the single parameter as 'Filter text (optional)', so the description meaningfully compensates by naming the six accepted filter dimensions (issuer, name, symbol, ticker, ISIN, FIGI). It could still clarify matching behavior (exact vs substring, multi-field), preventing a 5.

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 resource (securities in the Tokenized Asset Map) and enumerates what each record carries (FIGI, ISIN, chains). An agent can distinguish it from the singular get_tokenized_asset by the plural/collection framing, though the description never explicitly contrasts with siblings.

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 second sentence explains how to filter ('Optionally filter by issuer, name, symbol, ticker, ISIN or FIGI'), which implies usage, but there is no statement of when to reach for this list versus get_tokenized_asset or verify_asset_with_issuer.

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