get_stacking_rewards

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

With no annotations, the description carries the disclosure burden and does well: it explains that the amount is gross of the signer manager's fees, that it is unclaimed, and that two flags report whether the manager must still pull funds from pox-5 and whether an on-chain staker claim is supported. It doesn't explicitly say this is a read-only/no-state-change call or mention failure modes, which keeps it below 5.

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 definition is short and front-loaded, but the core sentence is a long run-on bundling three separate return values, and the trailing 'Tip' about earning_opportunities is tangential promotion that doesn't help call this tool correctly.

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?

There is no output schema, and the description compensates by describing the three pieces of returned information in prose (unclaimed amount before fees, pull-required flag, claim-support flag). For a 3-parameter read tool with no annotations, that is close to sufficient; only a pointer to the follow-up claim path 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 all three parameters (address, rewardCycle, signerManager) are documented there with defaults. The description only implicitly references them ('an address', 'one reward cycle', 'its signer manager') and adds no format, unit, or cycle-range detail beyond the schema, so the baseline 3 applies.

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+resource: it reads the PoX-5 sBTC rewards an address has earned but not yet claimed from its signer manager, plus two accompanying status flags. That is genuinely distinguishing information, but the sentence is convoluted and never contrasts itself with siblings like claim_stacking_rewards, dual_stacking_get_rewards, or get_stacking_status.

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?

There is no 'when to use' guidance at all — no statement about using this before claiming, or when to prefer it over claim_stacking_rewards / dual_stacking_get_rewards. The only routing hint is a 'Tip' pointing at earning_opportunities, which is promotional rather than a selection criterion.

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