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

Annotations already declare this as a read-only, idempotent, non-destructive, open-world operation. The description adds the useful detail that it returns token address and decimals, but it does not cover authentication, rate limits, pagination, or chain-specific behavior.

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, front-loaded sentence with no filler. It is appropriately sized for a search tool and immediately communicates the action and search surface.

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?

With no output schema, the description does describe the returned fields (address and decimals). However, it omits pagination behavior, chain scoping, and the role of the required direction parameter, leaving meaningful gaps for a five-parameter search tool.

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 description only restates the query semantics already documented in the schema (symbol, name, or address). It does not explain the required direction parameter nor the chainId, limit, or offset parameters, leaving 40% of parameters without descriptive support.

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 states a specific verb and resource: find a token address and decimals. It clearly explains what is searched by symbol, name, or address, but does not explicitly differentiate this tool from siblings like list_chains or get_quote.

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 usage when a token address or decimals is needed and the identifier is a symbol, name, or address. However, it offers no explicit when-to-use guidance, no exclusions, and no alternatives among the sibling tools.

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