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 partly covered, and the description correctly reinforces this with "Read-only." It adds genuinely new context the annotations lack: the required OAuth scope wallet:read, the guarantee of at least 30 days of epochs, and the inclusion of auto-claims in the provider-fee bucket. A small gap remains regarding pagination or how far back history extends beyond the 30-day floor.

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?

Two sentences: the first front-loads the verb, scope, time window and breakdown of reward categories; the second carries the safety and auth metadata. Every clause adds information an agent needs, with no restatement of the name or title.

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 carries the burden of describing return content, and it does so well: enumerated reward categories, cumulative validation rewards, and burn-window countdowns. It also names the required OAuth scope. The only missing piece is return-shape detail (field names, units, ordering), which keeps it short of a 5.

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 (schema coverage 100% with an empty properties object), so per the rubric the baseline is 4. The description also usefully clarifies that the target wallet is implicitly "the calling wallet," which is a meaningful detail beyond an empty schema.

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 uses a specific verb+resource ("Return the calling wallet's reward history") and immediately scopes what that history contains: FLR claimed per epoch split into FTSO delegation, P-chain staking and provider fees, plus cumulative validation rewards and burn-window countdowns. This distinguishes it clearly from siblings such as get_my_claimable (unclaimed amounts) and get_my_portfolio_summary (holdings), so an agent can route without opening schemas.

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?

Usage is implied by the possessive scope ("calling wallet's"), which signals this is the self-service history endpoint versus provider-side tools like get_ftso_provider_history. However, the description never states when to prefer this over get_my_claimable or simulate_delegation_rewards, and gives no exclusions or prerequisites beyond the OAuth scope. Adequate but with a clear gap in alternative routing.

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