get_claimable_rewards

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

Annotations already indicate read-only, idempotent, non-destructive behavior. The description adds value by detailing the return structure (map keyed by round with merkleIndex, amount, token info) and the intended follow-up action, which goes beyond what annotations provide.

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 that are front-loaded with the main action and result. Each sentence adds essential information: what it does, what it returns, and how to use it. No filler or redundancy.

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 explains the return format sufficiently. It also mentions mainnet-only and the follow-up tool. For a read-only query tool with annotations, this is complete.

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 covers both parameters (address and network) with descriptions. The description reinforces network must be mainnet but adds no new parameter meaning. Schema description coverage is 100%, so baseline 3 is appropriate.

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 scans all JustLend V1 merkle airdrop distributors for unclaimed rewards, and distinguishes itself from sibling tools like claim_v1_mining_period and other 'get_' tools by specifying the action and the follow-up tool. The verb 'scan' and resource 'JustLend V1 merkle airdrop distributors' are specific.

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 explains this tool is used before claim_v1_mining_period to obtain claimable rewards data. It also notes mainnet-only, providing clear context. It does not explicitly state when not to use it, but the context is sufficient.

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