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

readOnlyHint=true already tells the agent this is a safe read, so the lower bar applies. The description adds genuinely useful behavior beyond that: results are indexed (potentially stale) and a companion fresh-read path exists via state_call_id / results[].id joining. It stops short of saying how fresh the index is or what an empty result means, so it lands at a 3 rather than higher.

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 tight sentences: the what-and-what-returns comes first, the fresh-state escape hatch second. Dense identifier notation but nothing is filler; the only cost is that the second sentence requires decoding for an agent unfamiliar with the join keys.

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?

An output schema exists, so return values need not be spelled out, and safety is covered by annotations. However, for a tool with five parameters including state and chain filters, the description omits any guidance on filtering, pagination, or cross-chain behavior, which leaves a meaningful gap for correct 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?

Schema description coverage is only 40% (owner is just "address", page/page_size/state/chain_id carry no descriptions), so the description needed to compensate and does not — no parameter is explained. The only identifiers discussed (read_calls_reference, state_call_id) belong to the response shape, not the input schema.

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?

States a specific verb ("Enumerate") and resource ("an owner's indexed Ekubo position NFTs") plus the payload contents (pool keys, bounds, liquidity, pool state, rewards), which clearly separates this list-by-owner tool from the single-position sibling get_position. It does not explicitly name a sibling to contrast against, keeping it just below a 5.

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?

Gives an explicit conditional workflow: when fresh onchain state is needed, pass each current_state_reads[].read_calls_reference into wallet_batch_eth_call. That is real when-to-use guidance with a named alternative. It does not cover the state (opened/closed) filter or pagination choices, so exclusions are incomplete.

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