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

Annotations only declare readOnlyHint=true, and the description usefully confirms non-destructiveness ('keeping its liquidity and NFT') plus an owner-verification gate. However it leans on undefined terms ('its current_state_query', 'expected_owner') that are not parameters or schema fields, so the disclosed behavior is not fully actionable.

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 sentences, front-loaded with the outcome and then the pre-flight requirement; no filler. The second sentence is dense with conditional logic but still parses.

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 explained, and the mutation scope is covered. The gap is the reference to a 'current_state_query' and 'expected_owner' that have no counterpart in the input schema, leaving an agent unsure how to satisfy the stated precondition.

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 the baseline is 3. The description adds that the owner is validated against an expected value and that decoded amounts flow to 'the wallet' (loosely implying recipient), but it adds no format or default semantics beyond the 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 (prepare collection) and a precisely scoped resource: accrued fees from a standard LP position OR rewards from a Ve33 position, while preserving liquidity and the NFT. That scope statement is what separates it from collect/claim siblings, though it never names those siblings explicitly.

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 a concrete prerequisite sequence ('Run its current_state_query first', all inner calls must succeed, decoded owner must equal expected_owner), which is real when-to-use guidance. It never addresses when to prefer this over prepare_ve33_claim_fees, prepare_uniswap_v3_collect_fees, or prepare_rewards_claim, so alternative selection is left to inference.

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