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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds real value beyond that: it discloses the required OAuth scope (wallet:read) and explains the edge case that un-priced amounts appear in flr_pending_resolution rather than the main result.

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?

Front-loaded with the core purpose, then the returned data sources, then the pending-resolution caveat and auth requirement. It is one dense enumerating sentence plus a short second sentence — every clause carries information, though the enumeration is heavy.

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 and no parameters, the description carries the return-value burden and does so by naming the reward categories and the flr_pending_resolution field. It is nearly complete, though it does not mention whether amounts are formatted, token-denominated, or how empty results appear.

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?

The tool takes zero parameters, so per the rubric the baseline is 4. The description adds no parameter information because there is none to add, and nothing in it is misleading about inputs.

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 — 'Return what the calling wallet can claim right now' — and enumerates the exact reward sources (Flare FTSO delegation, P-chain staking mirror, provider fee/validation rewards, Songbird FTSO). The 'right now' framing distinguishes it from the sibling get_my_rewards_history without needing to name it.

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 implies usage (check current claimable balances) and names a prerequisite (OAuth scope wallet:read), but never says when to prefer this over get_my_rewards_history, get_my_portfolio_summary, or get_my_delegations. No explicit when/when-not routing is provided.

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