claimLiquidityInterest

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

With no annotations, the description carries the full burden. It discloses that the tool claims interest, credits to the default account, and that positionId is not required. However, it does not mention idempotency or behavior when no interest is available, but overall it is sufficiently transparent for a simple claim action.

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 extremely concise, with three bullet points and a rate limit note. Every sentence adds value, and the most critical information is front-loaded in the first sentence.

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 simple tool with one required parameter, the description covers all essential aspects: behavior, parameter usage, constraints, and rate limit. No output schema is provided, but that is not needed for a straightforward claim action.

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 input schema has one required parameter (productId) with 0% description coverage. The description adds meaning by explaining that productId='-1' claims all products, and that productId specifies the product. This provides essential context beyond the schema's basic type definition.

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 clearly states the tool's purpose: 'Claim all available interest for the specified product in one click.' It includes a special case for claiming all products at once, distinguishing it from related tools like 'reinvestLiquidity' or 'addLiquidity'.

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 provides explicit context on when to use the tool, including how to claim all products (productId=-1), that yield goes to the default account, and that positionId is unnecessary. It also specifies the rate limit, aiding the agent in selecting appropriate usage.

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