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

The annotations already declare readOnlyHint=true and destructiveHint=false, and the description's 'Read' verb is consistent with those. The description adds useful scoping ('non-stake', 'claimable by a beneficiary') but does not mention auth requirements, return format, or decimal/unit details.

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 front-loaded sentence that communicates the action, object, and relevant scope without filler. It does not duplicate schema or annotation information.

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 read-only tool with one required parameter and clear annotations, the description covers the core invocation context. Minor gaps remain around the meaning of 'non-stake' and the exact return shape, but they are not blocking for a simple claimable-balance lookup.

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%, so the schema already documents the required beneficiary address. The description simply echoes 'beneficiary' and adds no new parameter-level meaning, so it correctly relies on the 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 ('Read') and a specific resource ('non-stake USDC claimable by a beneficiary'), making the tool's purpose clear. It does not explicitly distinguish itself from sibling stake-related readers like peer_stake_balance or peer_stake_free, so it is clear but not fully differentiated.

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 when-to-use guidance, exclusions, or alternative tools are mentioned. The agent must infer from the word 'claimable' when this tool is appropriate, and the description does not explain why this is preferred over other peer_stake_* read tools.

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