get_moolah_pending_mining_periods

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false. The description adds behavioral details such as returning merkleIndex, index, amounts, proof, and USD total, and explains the includeClaimed parameter behavior. No contradictions.

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 three sentences, each earning its place: first sentence states purpose, second lists return fields, third explains usage and parameter. No superfluous text, and key information is front-loaded.

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?

Despite no output schema, the description compensates by listing return fields (merkleIndex, index, amounts, proof, total). It adequately covers the tool's behavior and parameter usage, though it doesn't mention pagination or error handling. Still sufficient for a read-only list tool.

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 100% with descriptions for all 3 parameters. The description adds extra meaning for includeClaimed (default false matches rewards card behaviour) and implies that address and network are optional. Baseline 3, plus 1 for additional context.

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 verb (Get), resource (claimable V2 mining airdrop rounds), and scope (already settled and merkle-published). It distinguishes itself from siblings like claim_moolah_mining_period and get_moolah_mining_accruing by specifying the state of the rounds.

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 explicitly tells the agent to feed periodKey into claim_moolah_mining_period for the next step, and explains when to use includeClaimed=true. While it doesn't explicitly list alternatives, the context from sibling tools and the focus on settled rounds provides clear usage context.

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