List every token quotable on Rialto for Robinhood Chain (symbol, address, decimals, type). Public endpoint; call this before quoting to resolve symbols and decimals.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Describes itself as a 'Public endpoint' and an idempotent list operation. While no annotations are provided, the description adequately conveys it is read-only and safe to call. Lacks explicit statement about no side effects but strongly implied.
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 concise sentences with no fluff. Action and key context are front-loaded. Every sentence adds value.
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?
Covers purpose, output fields, chain, public access, and sequential usage. For a tool with no parameters or output schema, the description is fully complete.
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?
No parameters in schema; description doesn't need to compensate. It adds value by explaining the output fields and context, which is sufficient for a baseline 4.
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?
Clearly states the verb 'list' and resource 'every token quotable on Rialto for Robinhood Chain', with specific output fields (symbol, address, decimals, type). Differentiates from siblings by indicating it is a prerequisite for quoting.
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?
Explicitly says 'call this before quoting to resolve symbols and decimals', providing a clear when-to-use directive. Also notes it is a public endpoint, implying no authentication needed.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool has a clearly distinct purpose: listing tokens, getting quotes, validating quotes, and building unsigned transactions. No overlapping functionality.
All tools use the 'rialto_' prefix and mostly follow a verb_noun pattern (list_tokens, get_quote, build_unsigned_tx). 'preflight' is slightly less conventional but still clear.
With 4 tools, the server is well-scoped for a read-only swap service, covering token discovery, quoting, preflight checks, and transaction building without unnecessary complexity.
The tool set covers the full workflow for a read-only swap server: token listing, quoting, validation, and unsigned transaction generation. No obvious gaps for the stated purpose.