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

With no annotations, the description carries the full load, and it does disclose the transport (native public Uniswap HTTP contract), that the caller's OpenAny gateway credentials are used, and that charges/authorization are gateway-determined. That is useful billing and auth context. What it omits is the actual behavior: whether this is a read-only approval check or submits anything, and that permitData / Permit2 flow can be toggled via the header.

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?

Three short sentences, front-loaded with the action before the infrastructure notes, with no redundancy. The gateway credential/billing sentences are somewhat boilerplate but still short and informative.

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?

This is a POST tool with a nested body, no annotations, and no output schema, and the description never says what comes back (approval status, permitData, transaction calldata) or what state, if any, is touched. For a swap-adjacent operation tied to wallet authorization, that gap matters more than the generic gateway notes.

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 reported at 100%, so the baseline is 3, and the x-permit2-disabled field in the schema already explains the Permit2 fallback in detail. The description adds no meaning about the required body fields (walletAddress, token, amount, chainId) or the urgency/gas options, so it relies entirely on the schema.

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?

"Check swap approvals" gives a clear verb and resource, and the mention of the native Uniswap HTTP contract scopes it to the Uniswap surface. It does not differentiate from the sibling uniswap_post_lp_check_approval (the LP variant), so an agent must infer the split from the name prefix alone.

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 statement of when to call this — e.g. before uniswap_post_v1_swap to see whether an approval is required — nor any exclusion against the LP counterpart or the wallet-delegation tools. The agent gets a capability but no routing logic.

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