executeLPStake

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

No annotations provided, so description carries full burden. Discloses that response is acknowledgment only, advises using getLPPositionList for confirmation, and mentions 10-60 second on-chain delay. Also warns about prerequisites and user confirmation requirement.

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?

Well-structured with purpose, prerequisites, warnings, and hints. Front-loaded with key info. Some repetition of 'user approval' but each section adds value. Could be slightly more concise, but overall efficient.

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?

Given 8 parameters, no output schema, and complexity, description is comprehensive. Explains workflow: verify balance, get pool info, display details, confirm, execute, then poll getLPPositionList. Mentions on-chain delay. Relates to sibling tools appropriately.

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 coverage is 0%, but description adds key parameter insights: positionId semantics, poolAddress, payTokenAmount, payTokenCode, and constraint to use either range or price pairs. Lacks full parameter descriptions but compensates with usage rules.

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: 'Execute LP stake to provide liquidity and earn rewards.' It returns a position ID for tracking. This distinguishes it from sibling tools like executeLPRedeem (redeem) and getLPPositionList (read).

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?

Provides explicit prerequisites: call getLPPayTokenList and getLPPoolInfo first, display details to user, obtain explicit confirmation. States 'Do NOT call this endpoint directly without user approval.' and gives parameter usage rules (positionId=0 new, non-zero adds; use range/price pairs, not both).

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