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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the safe, non-destructive nature is covered. The description adds value by revealing that the tool returns 'a normalized conditionalOrderHandoff' and that sellAmount can be a USD budget or 'max', which are behavioral details not present in the annotations.

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 two sentences long, front-loaded with the core purpose, and includes only essential details about sellAmount flexibility and the return type. Every sentence earns its place with no redundancy.

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?

The description mentions the return type (conditionalOrderHandoff) which compensates for the lack of an output schema. However, it does not explain how buy/sell token addresses are determined or what happens if they are omitted, which is a minor gap given the tool's complexity but not critical due to strong annotations and schema.

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%, and the schema already provides a detailed description for sellAmount (including USD budget and 'max'). The tool description restates this but adds no new parameter-level information beyond what the schema provides. Baseline 3 is appropriate.

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 opens with 'Quote an exact-input Ethereum swap,' which is a specific verb (Quote) + resource (Ethereum swap) + qualifier (exact-input). This clearly distinguishes it from sibling chain-specific tools like bscSwapQuote and polygonSwapQuote. The additional mention of 'explicit entry or exit orders' further clarifies its intended use case.

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 gives clear context by specifying 'exact-input' and 'explicit entry or exit orders,' which helps the agent understand when to use this tool. However, it does not explicitly contrast it with other swap quote tools or state when not to use it, so it falls short of a 5.

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