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

Annotations already declare readOnlyHint=true, idempotentHint=true, and openWorldHint=false, so the safety profile is covered. The description adds meaningful context beyond that: the data is 'static public reference info' and the tool is legacy, which tells the agent not to treat it as a live/authoritative source.

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 sentences, no filler, and the alternative-tool routing is placed last where an agent will see it. The long enumerated field list is dense but each item is informative; opening with the unexplained 'Legacy-available' is slightly awkward front-loading.

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 carries the burden of describing returns and does so thoroughly via the field enumeration, plus a cross-reference to get_asset_identity. It leaves 'legacy-available' undefined and doesn't say whether the data can be stale, which is the one remaining gap for a reference-data 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?

Zero parameters, so the baseline of 4 applies; there is no parameter surface for the description to clarify or obscure. The returned-field list is arguably return-value documentation rather than parameter semantics.

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 (static public reference info about the ASTEROID XRPL project) and enumerates exactly what it returns: issuer address, currency code, wallet roles/claim status, website, where to buy, socials, disclaimer. It also explicitly distinguishes itself from get_asset_identity, so an agent can separate it from the 14 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?

Gives a clear routing rule: 'For canonical machine identity prefer get_asset_identity,' which is exactly the when-to-use-this-vs-alternative guidance needed. It also flags 'Legacy-available,' hinting at deprecation status, but never states when this tool should still be called or what 'legacy-available' means operationally.

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