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

Annotations already declare readOnlyHint and openWorldHint, so the description's job is supplementary — and it delivers: it signals zero cost ('FREE'), no credential/secret requirements, and that balances are 'live' rather than cached. It does not cover pagination or how many payouts constitute 'recent', but the added context beyond annotations 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?

A single compact sentence with the most agent-relevant qualifier ('FREE') front-loaded and the no-secrets reassurance last. Slightly list-like and marketing-tinged, but no wasted words.

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, the description must convey return contents, and it does so comprehensively for a zero-parameter read tool. The only soft spot is 'recent payout history' — size, ordering, and truncation behavior are unspecified.

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 takes zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The description correctly implies a no-argument call and adds no misleading parameter talk.

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 identifies the resource — a public prize wallet — and enumerates what is returned (address, live USDC/SOL balances, autopay flag, payout history with Solscan links). It does not use a leading verb or explicitly distinguish itself from siblings like arena_leaderboard, but the subject matter is specific enough that an agent can tell it apart.

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?

There is no explicit when-to-use guidance and no mention of alternatives among the arena_* siblings. 'FREE' and 'No secrets' hint that this is a safe zero-cost public read, but the agent must infer that this is the tool for wallet/balance/payout checks rather than being told.

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