List Uniswap V3 positions

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

With no annotations provided, the description carries the behavioral burden. It discloses a notable cost ($0.01 USDG), which is important for an AI agent to know before invocation. It also specifies the output contents (tick range, liquidity, uncollected fees), adding transparency beyond a generic 'list' statement.

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 a single sentence that front-loads the action and resource. It includes the cost detail and output fields without wasted words, making it highly concise and well-structured.

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?

Given the tool's simplicity (one parameter, no output schema), the description adequately covers the key aspects: what it lists, for whom, and at what cost. It does not mention pagination or error behavior, but these are not critical for a basic read-only lookup tool with a well-defined single parameter.

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%: the single address parameter is already described with type and format ('Robinhood Chain address to look up (0x...)'). The description adds no extra semantic detail beyond the schema, so it meets the baseline but does not exceed it.

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 'Lists' and clearly identifies the resource: 'Uniswap V3 liquidity position NFT owned by an address on Robinhood Chain'. It also specifies the data returned (tick range, liquidity, uncollected fees), which distinguishes it from sibling mutation tools like liquidity_add and liquidity_remove.

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 implies the tool is for viewing an address's liquidity positions but does not explicitly state when to use it versus alternatives or provide exclusions. It is clear enough for a simple read operation but lacks explicit guidance about sibling tools like liquidity_add or liquidity_remove.

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