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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds genuinely non-obvious domain context: these records are off-chain until the player claims them, and the result reflects claim status — information an agent could not infer from the annotations.

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?

One front-loaded sentence plus a short caveat about on-chain status; no filler. The main sentence is slightly convoluted ('and which were claimed') but every clause carries 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?

With no output schema and no annotations beyond read-only, the description should say more about the returned shape (awards, claim status, counts) and behavior for unknown players or empty results. It conveys the concept but leaves the agent guessing at the result surface.

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 0%, so the description must carry the load. It does clarify that playerId is opaque and that email is an alternative identifier, but it never states whether one is required, whether both may be supplied, or what happens if neither is given (required count is 0). Partial compensation only.

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?

States a specific verb+resource: listing pending soulbound awards recorded for one player, identified by playerId or email. It clearly delimits the scope to a single player's off-chain pending awards, though it does not explicitly name which sibling (e.g. my_soulbound_usage or verify_soulbound_holder) covers adjacent questions.

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 the tool applies (viewing a player's pending, unclaimed awards) but never says when to prefer it over siblings or what prerequisites exist. There is no statement about required auth/link-owner scope beyond the passing phrase 'the link owner recorded'.

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