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

Goes well beyond the annotations (which only declare readOnly/openWorld/non-destructive) by disclosing concrete rate limits (20/min, one call per 3s), the absence of RPC access to broadcast claims, and the exact semantics of a missing claimTransaction (nothing claimable, e.g. still vesting). It even flags the subtle trap that `to` is the RebalancingManager contract, not the item's own `distributorAddress`.

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 deprecation warning and core purpose are front-loaded, and the dense claimTransaction guidance earns its space for a tool whose consumers must broadcast on-chain. There is mild redundancy, however — the server's inability to claim is stated more than once ('this server cannot claim rewards for you' / 'cannot do it for you').

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 available, the description carries the full burden and delivers, describing the return shape (rewards[].rewardItems[] with available balances and optional claimTransaction carrying to/abi/calldata) and the meaning of missing fields. Nothing an agent needs to interpret results or act on them is missing.

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% and both parameters (walletAddress, reloadChain) are fully described in the schema, so the description does not need to re-explain them. It adds no extra syntax or format detail for either parameter, making the baseline 3 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?

States a specific verb and resource ('Get a wallet's aggregated rewards/earnings across all reward sources'), and explicitly delimits scope against the sibling get_balances ('Does NOT include base rebalancer yield/APY earnings — those are in get_balances' netEarning field'). It also flags the tool as DEPRECATED up front, so an agent can differentiate it without opening a schema.

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?

Gives clear context: it tells the agent what the tool covers, what it excludes (base yield lives in get_balances), and that no claim can be submitted server-side, so the agent knows this is read-only discovery. The main gap is that the [DEPRECATED] tag names no successor tool, leaving the agent to infer the replacement.

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