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

With no annotations present, the description carries the full behavioral burden. It discloses that the program is immutable, mints earnings to the wallet, is purely on-chain, requires the user to construct and sign the transaction, and involves no server. This is significant behavioral context with no annotations behind it.

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 compact and front-loaded: it identifies the action first, then provides the necessary context about earning, minting, and on-chain execution. Every sentence contributes meaning and there is no irrelevant filler.

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 covers the necessary context: the reward mechanism, the claimed outcome, the on-chain nature, and the user-authorization requirement. The agent has enough information to decide when and how to invoke it.

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?

There are zero parameters, so the baseline is 4. The schema already covers 100% of the input contract, and no additional parameter semantics are needed.

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 (claim) and resource ($SPIN) and states the exact purpose: claiming earned rewards from CAPYSLOT spins. This clearly differentiates it from siblings like capyslot_play and casino_state by naming the claim-without-spin action.

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 the right trigger clearly: after CAPYSLOT or spins earn $SPIN, this tool claims them. It does not name an alternate tool or explicitly say when not to use it, but 'what you have earned' gives enough context to know this is the claim step.

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