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

With no annotations, the description carries the full burden. It discloses that num_swaps and fee_accrual_rate_recent are V2-only and return null for V3, and that a single-block live snapshot returns null for LP-concentration and swap metrics because they are unrecoverable from state. These are significant behavioral caveats not evident from the schema 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 concise and front-loaded with the primary purpose, followed by metric details and caveats. Each sentence adds value: purpose, metric list, V2/V3 distinction, and null behavior. There is no redundancy or filler.

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 no output schema, the description explains what metrics are returned and when they are null, which is substantial context. However, it does not describe the return value structure or error handling, and the schema's pool_address description mentions Balancer/Curve pools, which conflicts with the stated V2/V3-only scope, leaving slight ambiguity.

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 provides 100% description coverage for all 6 parameters, so the baseline is 3. The description adds little beyond the schema—it mentions that recent_window is V2-only and defaults to 20, but this is already present in the schema. No additional parameter semantics are provided.

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 clearly states the tool snapshots pool-level health metrics for Uniswap V2/V3 pools and lists specific metrics (TVL, reserves, fees, LP concentration, swap activity). It distinguishes from position-level analysis and sibling tools by specifying the pool-level scope and protocol focus.

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 clearly indicates the use case: answers 'is this a pool I would deposit into?' at the pool level, not position level. This implies when to use it, but it does not explicitly name alternative tools or state when not to use it beyond the pool vs position distinction.

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