Search 8DX Tokens

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

With no annotations provided, the description carries full responsibility for behavioral disclosure. It accurately indicates this is a search (and therefore likely read-only), but it does not explicitly state safety/auth implications, return value details, or any rate limits. It adds some context but leaves the agent without full transparency beyond the basic operation.

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 a single sentence that is front-loaded with the core action ('Searches 8DX token metadata') and immediately clarifies the use case. Every word earns its place, with no redundant or vague phrasing.

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?

While the description clearly conveys the tool's purpose and when to use it, it does not explain what the search returns (e.g., the structure of token metadata) or provide details about pagination/ordering beyond what the schema already includes. With no output schema, the description should say more about the response format to be 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?

The schema covers 100% of parameters, but the description adds meaningful context for the 'q' parameter by explaining it resolves user phrases like 'BTC, bitcoin, USDC, or a token name.' This goes beyond the schema's 'Token symbol, name, or address search query' and helps the agent know how to construct queries.

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 a specific verb and resource: 'Searches 8DX token metadata.' It clearly distinguishes this tool from sibling tools by focusing on token resolution/search rather than quoting or swapping, and provides concrete examples (BTC, bitcoin, USDC) that illustrate its purpose.

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 description explicitly states the intended usage context: 'so an AI agent can resolve user phrases ... before quoting.' This gives clear guidance on when to use the tool, though it does not explicitly mention when not to use it or name alternatives, stopping short of a 5.

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