claim-rewards

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 states 'claim rewards' which implies a write/transaction operation, but doesn't disclose critical traits: whether this requires authentication, has side effects (e.g., on-chain transaction), involves fees, is irreversible, or has rate limits. For a mutation tool with zero annotation coverage, this is a significant gap in transparency.

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 description is a single, efficient sentence that directly states the tool's purpose without unnecessary words. It's appropriately sized and front-loaded, though it could be slightly more informative without losing conciseness (e.g., by hinting at transaction behavior).

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?

Given the complexity of a blockchain transaction tool with no annotations and no output schema, the description is incomplete. It doesn't address key contextual aspects: what the tool returns (success/failure, transaction hash), error conditions, or behavioral implications (e.g., that it's a write operation). This leaves gaps for the agent to understand the tool's full impact.

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 description coverage is 100%, with clear descriptions for all three parameters in the input schema (e.g., 'operatorAddress' as the validator address, 'networkName' with usage instructions). The description adds no additional parameter semantics beyond what the schema provides, so it meets the baseline of 3 where the schema does the heavy lifting.

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 rewards') and the target resource ('for a specific validator'), which provides a specific verb+resource combination. However, it doesn't explicitly differentiate from sibling tools like 'get-available-rewards' or 'undelegate', which would require mentioning what makes this tool distinct (e.g., that it's a transaction vs. a query).

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?

No guidance is provided on when to use this tool versus alternatives. The description doesn't mention prerequisites (e.g., needing available rewards first), exclusions, or comparisons to siblings like 'get-available-rewards' (which might check rewards before claiming) or 'delegate' (which involves staking). This leaves the agent without context for tool selection.

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