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

Beyond the readOnlyHint annotation, the description discloses that the tool includes a pending current-state read and explains how to resolve it with wallet_batch_eth_call and state_call_id joining. It does not cover error behavior, prerequisites, or limits, but the operational follow-up detail is substantial.

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 compact and front-loads the core action, with a necessary second sentence explaining the current_state_query handoff. The first sentence is dense with returned fields, which slightly reduces readability, but there is little unnecessary 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 read-only position-detail tool with an output schema and 100% input schema coverage, the description covers the key behavior and the non-obvious wallet_batch_eth_call follow-up. It is nearly complete, though it lacks explicit sibling routing and does not clarify whether current_state_query is always present.

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 100%, so all four required inputs are already documented in the schema. The description does not add syntax, constraints, or selection meaning for owner, chain_id, positions_address, or token_id beyond what the schema provides, so 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 states a specific verb and resource: hydrate one owner position, and enumerates the included data such as pool key, bounds, liquidity, metadata, history, rewards, and prices. It implicitly distinguishes single-position hydration from bulk lookup via 'one owner position', but it does not explicitly name distinguishing siblings like get_positions_by_owner.

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 procedural guidance for resolving current_state_query via wallet_batch_eth_call in the same code block, which is useful. However, it does not state when to choose this tool over get_positions_by_owner or get_position_pool_candidates, so alternatives remain implied rather than explicit.

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