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

Goes well beyond readOnlyHint=true: it discloses filtering rules (native units only counted 'when the unit and its pool name each other on the ledger'; Precision collections only if minted by a real PrecisionPool that names them), that fees and withdrawal returns are 'simulated with the real transactions', how 7/30-day change is computed (geometric mean, ledger state as it was then), and the operational meaning of out-of-range positions ('earns no fees until the price comes back'). This is exactly the kind of context annotations cannot carry.

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?

Every clause is informative, but the content is delivered as a single sprawling sentence with nested parentheticals, so no single fact is front-loaded and the reader must parse clauses to find the scope. It is dense rather than tight; splitting the native-pool and Precision portions into separate sentences would preserve all substance and improve scanability.

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?

There is no output schema, so the description must describe return contents — and it does thoroughly: per-unit redemption value, pool share, DEX listing and reported APR, 7/30-day value change, claimable fees, withdrawal simulation results, and in-range status. An agent can predict the shape of the response without opening anything else.

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% and both parameters (account address format, mainnet/stokenet enum) are fully documented in the schema, so the baseline 3 applies. The description adds nothing about the network parameter's effect on results or about address-format expectations.

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 opening clause ('Everything an account has in pools') plus the explicit enumeration of the two position families (native pool units, Ociswap Precision concentrated-liquidity NFTs) makes the resource unmistakable and clearly distinct from siblings like get_pool_state or find_pools. It loses a point because the purpose is embedded in a very long run-on sentence rather than stated as a crisp verb+resource up front.

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 downstream routing: 'Use build_dex_manifest to act on them, build_pool_manifest "redeem" for native units', which tells the agent what to do after reading. It does not, however, say when to prefer this over get_pool_state or find_pools, nor state any exclusions or prerequisites (e.g. account must be on the given network).

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