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

With no annotations provided, the description carries the full burden. It discloses the read-only nature (a feed), the fields returned (including a rug-blocklist flag), and the cost ($0.004 USDC). It could go deeper on rate limits or the exact rug-blocklist algorithm, but it adds meaningful behavioral context beyond just 'explore tokens'.

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?

The description is front-loaded with a clear purpose, followed by concise parameter semantics, and closes with price and feedback short-hook. It is slightly verbose with promotional phrasing ('discovery with a trust signal built in'), but every sentence contributes useful information and the structure is easy to scan.

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?

Given the lack of annotations and output schema, the description is remarkably complete: it specifies tool function, all parameters with allowed values, the exact fields in each row, the pricing model, and follow-up actions (check_xrpl_token, submit_feedback). An agent has enough context to decide when to call this tool and how to construct a proper request.

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 description coverage is 0%, so the description must fully explain parameters. It does: sort values are enumerated, query searches by name, limit/offset page, and trust_only filters to XRPLMeta-verified tokens. This adds far more than the schema alone, which lacks enum definitions or descriptions.

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?

The description opens with 'Discover XRPL tokens' — a clear verb and resource — and distinguishes itself from sibling tools like check_xrpl_token by framing itself as a broad feed ('DexScreener-style over 160k+ tokens'). This makes it obvious what the tool does and how it differs from more targeted tools.

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?

It provides explicit usage context: sorting options, search by query, pagination with limit/offset, and the trust_only filter. It also points to alternatives (check_xrpl_token for full verdict, submit_feedback for missing features). However, it does not explicitly state when NOT to use this tool versus alternatives, leaving a small gap.

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