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

With no annotations present, the description does add genuinely useful context the schema cannot: requests go through the native public Uniswap HTTP contract, use the caller's OpenAny gateway credentials, and charges/authorization are gateway-determined. That covers billing and auth, but it does not state that this is a non-destructive read, nor anything about rate limits or response shape.

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?

Four short sentences with the action front-loaded and the deployment/billing context following. Slightly boilerplate in the credential and charging sentences, but nothing is redundant or padded.

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 zero-required-parameter lookup with no output schema, the description covers how the call is billed and authenticated but omits what actually comes back (chain names, IDs, or identifiers) and whether the list should be cached — details an agent would otherwise have to discover by calling.

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 description coverage is nominally 100%, but the coverage is vacuous — the single optional x-agent-info parameter is described only as 'x-agent-info'. The description says nothing about this parameter or about the absence of required arguments. Per the high-coverage baseline this lands at 3, though the practical value is closer to 2.

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 clear verb and resource (get supported chains) that matches the tool name, but it gives no scope detail such as whether these are swap-routable chains, chain IDs, or Uniswap deployment networks, and it offers no differentiation from sibling chain-listing tools like lifi_get_v1_chains or goplus_get_api_v1_supported_chains.

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?

There is no guidance on when to call this versus alternatives, no prerequisite steps, and no indication of whether this should be called before a quote/swap request to validate a chain. Usage must be inferred entirely from the name.

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