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

Annotations already mark it read-only and non-destructive, and the description adds meaningful behavior beyond that: it covers both Merit-distributed and protocol-native incentives, explains chainsNotServed semantics, notes that repeated queries on unsupported chains return the same empty result, and calls out the extra claim transaction on v3 responses. This is substantial non-obvious 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 dense but front-loaded with the core purpose, followed by high-value edge-case guidance. Each sentence adds distinct information, and no filler or restatement of the name appears.

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?

With no output schema, the description nevertheless conveys the key return semantics: chain coverage fields, per-row chain IDs, unsupported-chain behavior, and the v3 transaction addition. It gives an agent enough context to call the tool correctly and interpret ambiguous empty results.

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?

Input schema coverage is 100%, so all three parameters are already documented. The description restates the omit-chainId behavior and default all version already present in the schema, and the main added value is response-shape context (chainsCovered, per-row chainId, v3 transaction) rather than new parameter meaning.

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 opening sentence identifies the tool as returning a wallet's claimable Aave rewards on v3, v4, or both, with a specific noun-verb-resource structure. It also states which incentive programmes are included, distinguishing this read tool from reward-related actions like prepare_claim_rewards.

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 gives concrete invocation guidance: omit chainId to cover all chains, interpret chainsNotServed as unsupported chains, and treat empty results there as non-answers. It does not explicitly name alternative tools or state when not to use it, so it stops short of a full 5.

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