claim_moolah_mining_period

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

Discloses on-chain pre-checks (isClaimed, merkleRoots) to avoid gas waste on reverting transactions. Annotations already mark destructiveHint=true, but the description adds valuable context about gas-saving behavior and current network restrictions.

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 sentences efficiently convey purpose, usage options, pre-checks, and network status. Front-loaded with core action, no wasted words.

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?

Thoroughly covers all aspects needed for an agent to use the tool: method, input options, pre-checks, and current deployment status. No output schema needed since it's a mutation.

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 provides full parameter descriptions (100% coverage). The description adds value by highlighting periodKey as preferred and explaining how override params work. Slight deduction because the schema already does heavy lifting.

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?

Clearly states it claims a single V2 mining airdrop round via multiClaim(). Distinguishes from sibling claim_v1_mining_period by specifying V2 and referencing get_moolah_pending_mining_periods for periodKey.

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?

Explicitly recommends using periodKey from get_moolah_pending_mining_periods or supplying override params directly. Warns about mainnet error and suggests nile testnet as alternative. Provides clear when-to-use and current limitations.

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