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

With no annotations, the description carries the full burden, and it does disclose the most important behavioral trait: this call only builds/reads LP operation data and does not sign or broadcast. It also tells the agent that authorization and charges come from the OpenAny gateway, which explains billing and credential behavior. It omits what a successful response contains (calldata, tx object?) and whether the claim transfers tokens or is reversible.

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?

Three short sentences, front-loaded with the operation and immediately followed by the build-vs-broadcast caveat. Little waste; the gateway sentence earns its place by explaining credential and charge behavior, though it could be compressed.

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 nested-body LP mutation with no annotations and no output schema, the description covers the credential and non-broadcast model but leaves gaps: what the response yields, whether the position must exist, whether approval is a prerequisite, and the effect of collectAsWeth/simulateTransaction. Adequate but not complete for the tool's complexity.

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 description adds zero parameter-level meaning: it never mentions tokenId, chainId, protocol (V3/V4), collectAsWeth, or simulateTransaction. The schema's own descriptions are vacuous ("body", "x-agent-info"), so the 100% coverage figure is misleading—the semantically loaded fields like collectAsWeth and simulateTransaction are undocumented anywhere, which an agent needs to avoid a mis-call.

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 first sentence gives a specific verb and resource ("Claim LP position fees"), which is clearly distinguishable from the other uniswap lp siblings (create, increase, decrease, pool_info, check_approval). It stops short of explicitly contrasting itself with those siblings, but an agent can identify the operation from the description alone.

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 implies the usage context by stating that signing and on-chain broadcasting are separate, which tells the agent this tool produces LP operation data rather than executing a transaction. However, it never states when to pick this tool over e.g. uniswap_post_lp_check_approval or uniswap_post_lp_decrease, nor any preconditions such as requiring an existing position or prior approval.

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