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

With no annotations, the description carries the full behavioral burden and does so: it discloses that a pinned quote is obtained, that Factory/QuoterV2/Pool/Router runtime identities are re-verified, that the return is unsigned approval plus swap calldata, and explicitly that it never receives a key, signs, relays, or broadcasts. This is a complete safety and output profile.

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?

Two sentences, zero filler, and the operative purpose is front-loaded before the behavioral and safety disclosures. Each sentence contributes distinct information.

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 5-parameter tool with full schema coverage and no output schema, the description covers purpose, verification behavior, return shape (unsigned approval and swap calldata), and non-custodial guarantees. It omits failure modes such as quote unavailability or allowlist rejection, which an agent preparing a transaction would benefit from knowing.

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 100%, so the schema already documents amountIn, recipient, maxSlippageBps, deadlineUnixSeconds, and profileId. The description adds only directional context (exact-input, USDC in / USDT out, single allowlisted pool) and no per-parameter semantics beyond what the schema provides. Baseline 3 applies.

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 first clause states a specific verb, resource, and scope: prepare a user-signable exact-input swap against one allowlisted Base PancakeSwap V3 pool. That is enough to distinguish it from sibling preparation tools such as prepare_aerodrome_slipstream_swap (different venue) and from read-only market tools like get_pancakeswap_v3_market.

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 establishes clear context for use: exact-input direction, single allowlisted Base PancakeSwap V3 pool, unsigned output for a user to sign. It does not, however, name a sibling alternative or state when NOT to use it (e.g., use get_pancakeswap_v3_market for quotes-only, or the Aerodrome variant for a different venue).

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