get_supported_tokens

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

Without annotations, the description carries the burden of behavioral disclosure. It mentions the return includes 'token symbol, name, address, and chain availability,' which is helpful. However, it does not state that the operation is read-only, idempotent, or any potential side effects. The absence of annotations makes this a moderate score.

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 concise with two sentences. The purpose is front-loaded: 'Search for tokens supported by Relay across chains.' Every sentence adds value without redundancy. Excellent structure.

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 4 parameters, no output schema, and no annotations, the description provides basic return info but omits details like result format, pagination, sorting, or error handling. It covers the minimum but leaves gaps for an agent needing precise behavioral understanding.

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 coverage is 100% with clear parameter descriptions. The tool description does not add new meaning beyond what the schema provides; it only summarizes the return. Baseline 3 is appropriate as the description adds no extra 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?

The description clearly states 'Search for tokens supported by Relay across chains' with a specific verb and resource. It explains the use case: 'find token contract addresses before getting quotes.' However, it does not explicitly differentiate from sibling tools like get_token_details or get_trending_tokens, missing a clear contrast.

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 provides clear context for when to use: 'before getting quotes.' This gives a specific workflow guidance. However, it does not mention when not to use or list alternatives among the many sibling search tools.

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