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

With no annotations provided, the description carries the full behavioral burden and does it well: 'read-only', 'No tokens move', and 'execution happens in the agent's own wallet/canister' make side effects unambiguous. It stops short of caveats like quote expiry or slippage, but for a non-mutating quote tool the disclosure is strong.

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 front-loaded sentences cover purpose, side-effect safety, and token-format guidance in a logical order. Apart from the minor 'deepest on-chain DEX' color phrase, every sentence earns its place.

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 and fully self-documenting schema together cover invocation essentials: quote direction, non-mutating behavior, accepted token formats, and base-unit amounts. There is no output schema, so exact response shape is unspecified, but the return concept is intuitive and the fee-tier fallback is already documented in the parameter 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?

The schema already documents all four parameters with 100% coverage, so the baseline applies. The description adds limited value by narrating the pay/receive relationship and giving concrete symbol examples, but mostly it restates schema-level information rather than exposing new parameter constraints.

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 a specific verb and object: 'Get a live, read-only swap quote on ICPSwap' and defines exactly what is returned ('how much receive_token you would get for pay_amount of pay_token'). It clearly separates this pricing tool from the unrelated wallet/deploy/faucet siblings.

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?

It gives clear context: this prices intent only, no tokens move, and execution happens in the agent's own wallet/canister, which tells an agent when to call it and that it has no on-chain side effects. It does not explicitly name an alternative quote/execution tool, but none of the listed siblings competes with it.

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