x402_lp_farm_unstake

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

With no annotations provided, the description discloses important behavioral details: the cost (paid USDC and ALGO fee), the single-transaction group structure, and the signing flow. It does not mention side effects like token return or failure modes, but the fee and process transparency is valuable.

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 a single sentence that front-loads the cost and transaction type, making it compact. However, the code-like notation reduces readability, and terms like '1-txn group' and 'appl' are not explained, making it less accessible than it could be.

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?

The description covers the transactional flow, cost, and required submit step, which is significant given the absence of an output schema. It does not explain the consequences of unstaking (e.g., tokens returned to sender) or any preconditions, leaving some context gaps for a financial operation.

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 schema already provides 100% description coverage for all three parameters (address, uint64, uint64 LP base units). The description only references unstakeAmount in the appl call and adds no new semantic detail beyond the schema, matching the baseline for full schema coverage.

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 identifies the action via 'lp-farm/unstake' and the appl call 'unstakeTokens(unstakeAmount)', making the resource and operation clear. It is somewhat jargon-heavy and lacks a plain-language statement, but it distinguishes from sibling stake/claim tools by naming the unstake action.

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 mentions a required follow-up ('call the submit tool') but provides no guidance on when to use this tool versus alternatives like x402_staking_unstake or when staking might be more appropriate. It does not state prerequisites such as having an existing LP farm position.

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