get_token_metadata

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

No annotations are provided, so the description carries the transparency burden. It adds a cost disclosure ($0.002 per request), which is useful, but does not mention read-only nature, error handling, or response format. However, 'get' implies a safe read operation, and the cost is a meaningful behavioral detail.

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 one sentence and front-loads the core function, with cost appended. Every word earns its place, and it is immediately clear what the tool does.

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?

For a simple metadata tool, the description gives the gist but omits the fact that at least one of id/slug/chain+address is needed. Without an output schema, it does not indicate the return structure beyond the examples. Still, it is adequate for a low-risk read operation.

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 descriptions cover all four parameters, so the baseline is 3. The description does not add additional parameter meaning, such as the requirement to provide at least one identifier. The schema already documents each parameter's purpose, so the description adds no extra value here.

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 clearly states the tool retrieves token metadata, listing concrete examples (name, symbol, decimals). This distinguishes it from price-focused sibling tools like get_token_prices and get_crypto_price. The verb 'get' and resource 'token metadata' are specific and unambiguous.

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 implies the tool is for metadata lookup, which differentiates it from price/history tools, but it does not explicitly state when to use it or name alternatives. There is no guidance on which parameter combination is required (e.g., chain+address vs id), but the context is clear enough for basic use.

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