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

Beyond readOnlyHint, the description adds that V3 collect has no onchain deadline and that the result should be regenerated and simulated before execution. It also discloses the optional WETH unwrapping behavior and the need to verify NFT ownership and currencies. These are meaningful operational constraints not conveyed by the annotation alone.

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 three tight sentences: purpose first, then preconditions, then execution guidance. Every sentence adds useful information without redundant wording.

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 prepare-transaction tool with seven parameters and an output schema, the description supplies the essential purpose, preconditions, and unique V3 deadline behavior. It does not explain the chain_id enum or sender role, but those remain documented in the schema and are not critical to safe invocation.

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 description maps unwrap_native to optional WETH unwrapping, token_id to NFT ownership, and token0/token1 to currencies. It also explains that V3 collect has no onchain deadline, which clarifies the unusual required deadline parameter. Schema coverage is 71%, and the description compensates for key parameters but does not cover chain_id or sender.

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 states a specific verb and resource: collect all owed fees from a Uniswap V3 position without removing liquidity. It distinguishes the action from liquidity removal, which is a key sibling operation, and explicitly names the V3 collect context.

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 preconditions—verify NFT ownership and currencies first—and a post-preparation workflow: regenerate and simulate before execution. It also clarifies that liquidity is not removed, which implicitly distinguishes this from remove-liquidity tools. It stops short of naming an explicit alternative or stating when not to use the tool.

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