claimRewards

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does well: it states that the tool checks the claimable balance first and skips the transaction if nothing to claim, which is a non-obvious behavioral trait. It also explains the reward-earning mechanism (epoch uptime and minimum position thresholds). However, it doesn't disclose whether the claim is a state-changing transaction (it is, by implication), whether it requires any authentication, or what the return value looks like. Still, for a zero-parameter tool, this is solid.

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 sentences, each earning its place: the first states the action and target, the second discloses the conditional skip behavior, the third explains how rewards are earned. No fluff, no repetition of the name, and the most important behavioral detail (skip if nothing to claim) is front-loaded in the second sentence.

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?

For a zero-parameter, no-output-schema tool, the description is nearly complete. It explains what the tool does, the precondition, and the reward mechanism. The only missing context is what happens after a successful claim (e.g., where the rewards go, whether there's a transaction hash returned) and whether there are any risks (e.g., gas costs). But given the tool's simplicity and the absence of annotations, this is a strong showing.

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 has zero parameters, so the schema is trivially complete (100% coverage). The description adds context about what the tool operates on (the MCP wallet's accrued rewards) and the condition for action (claimable balance > 0). Since there are no parameters to document, the description's job is to explain the tool's behavior, which it does. Baseline 4 for zero params is 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?

The description clearly states the action (claim), the resource (accrued KSKD rewards for the MCP wallet), and the mechanism (RewardsController). It also explains the precondition (checks claimable balance first) and the reward-earning context, which distinguishes it from sibling tools like getUserRewards (which likely only queries rewards) and stakeKSKD/unstakeKSKD (staking operations).

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 when to use this tool: when there are accrued KSKD rewards to claim. It explicitly states that it skips the transaction if nothing to claim, which is a clear behavioral guideline. However, it doesn't explicitly name alternatives like getUserRewards for checking rewards first, nor does it state when not to use it (e.g., if the user wants to check rewards without claiming). This is a minor gap.

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