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

With no annotations provided, the description carries full burden and succeeds: it discloses that the tool obtains a pinned quote, re-verifies contract identities (Factory, QuoterV2, Pool, Router), returns only unsigned approval and swap calldata, and never receives a key, signs, relays, or broadcasts. This gives the agent a complete safety and side-effect 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?

Four sentences, front-loaded with purpose, then inputs and internal checks, then return values and safety guarantees. Every sentence adds distinct value with no repetition or padding.

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 covers what the tool does, what it returns, and what it never does—sufficient for a preparation tool with no output schema. It could be slightly more explicit about the structure of the returned calldata or failure modes (e.g., what happens if the pool is not allowlisted), but the core behavioral contract is clear.

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%, so each parameter is already documented in the input schema. The description summarizes the parameters (reviewed profile id, exact input amount, recipient, short deadline, slippage bound) and adds minor linking context, but no new semantics 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 uses a specific verb ('Prepare') and resource ('user-signable exact-input swap against one allowlisted Base Aerodrome Slipstream pool'), clearly distinguishing it from siblings like get_aerodrome_slipstream_market or prepare_hyperliquid_perp_order. An agent can immediately tell this is a swap-preparation tool, not a market data or execution tool.

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: it prepares an unsigned swap for a reviewed profile id, with short deadline and slippage bound. It doesn't explicitly name alternatives or say when not to use it, but the scoping to 'one allowlisted pool' and the return of 'unsigned calldata only' implicitly routes the agent away from tools that broadcast or query markets.

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