claim_moolah_mining_period

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

Beyond annotations (destructiveHint=true), the description reveals pre-checks to avoid wasted gas: 'Pre-checks isClaimed() and merkleRoots() on-chain so the wallet does not pay gas for a guaranteed-revert tx.' It also notes that mainnet currently errors, which is critical behavioral context.

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 two sentences plus a warning, each sentence carrying essential information. It is front-loaded with the core action, no redundant words, and well-structured for quick comprehension.

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 purpose, usage, pre-checks, and network caveats. However, it lacks explicit mention of return value (e.g., transaction receipt), which would enhance completeness given no output schema. Overall, it is still highly informative.

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?

With 100% schema coverage, the description adds significant meaning: it explains the relationship between 'periodKey' (preferred) and the override parameters, and clarifies 'address' defaults to the signing wallet. This aids correct parameter selection beyond schema descriptions.

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 action ('Claim'), resource ('V2 mining airdrop round'), and method ('multiClaim() on the Moolah merkle distributor'). It distinguishes from sibling 'claim_v1_mining_period' by specifying 'V2' and the distributor, making the purpose unambiguous.

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 usage guidance: 'Pass periodKey from get_moolah_pending_mining_periods (preferred) or supply merkleIndex / index / amounts / proof directly.' It also warns about mainnet vs nile testnet, which helps the agent decide when to invoke. However, it does not compare directly with sibling tools like 'claim_v1_mining_period'.

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