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

With no annotations, the description carries the full burden and does well: it declares the data is read-only reference data, explains the authenticity guarantee (mints proven against the issuer's own domain), and disclaims it as non-advice. It omits whether any auth is needed, but the safety and provenance profile is clearly conveyed.

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?

Three sentences, front-loaded with the resource definition before the optional filtering and scope caveats. The first sentence is dense but every clause (issuers, examples, authenticity) earns its place; minor redundancy in the closing caveats.

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 annotations and no output schema, the description adequately covers what the tool returns (registry entries whose mints are verified) and its scope limits. Return-shape detail is light, but nothing critical for correct invocation is missing.

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 enum values and per-parameter descriptions, so the schema already does the heavy lifting. The description only restates that filtering by category or issuer is available, adding no syntax or format detail 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 resource (openly transferable tokenized real-world assets on Solana) with concrete examples (tokenized gold, US Treasuries, equities/ETFs) and names the issuers covered. It is clearly a listing endpoint distinct from the singular get_rwa, but it never names that sibling to sharpen the contrast.

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?

Notes that category/issuer filtering is optional and clarifies scope with 'not limited to what the vault itself holds', which implicitly routes agents away from vault-holdings tools. However, it does not explicitly say when to use this versus get_rwa or get_rwa_performance, leaving the choice to inference.

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