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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description still adds real value: the data source (RewardManager contract), the assurance that nothing is signed or stored, and the fact that claiming is out of scope and must be done by the owner. It does not discuss rate limits or failure modes for invalid addresses, but for a simple read that is minor.

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?

Three short sentences: what it returns, the data source, then the read-only/claiming constraint. Scope is front-loaded and no sentence is filler — the final sentence actively prevents an incorrect expectation of on-chain action.

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 return-shape burden and does so ('total, how many reward epochs, and when the oldest one expires'). Combined with the read-only disclosure and the wallet-claim boundary, an agent has everything needed to call it correctly and interpret 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?

Schema coverage is 100%, so both parameters are already documented, including the chain enum and its default. The description reinforces the chain scope ('Flare and/or Songbird') but adds no syntax or format 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?

Names a specific verb+resource (FTSO delegation rewards claimable for an address) and scopes it to Flare and/or Songbird, read from the RewardManager contract. It also previews the return shape (total, epoch count, oldest expiry). It stops short of explicitly contrasting with the sibling get_reward_deadlines, whose territory ('when the oldest one expires') partially overlaps with the deadline information described here.

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 for use ('rewards an address can claim right now') and an explicit boundary: this tool does not claim, the owner must claim in their own wallet. That negative framing prevents a common misuse. Missing only an explicit named alternative for deadline-centric questions.

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