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 that reads cost nothing ('Free') and that the payload splits into owed versus paid amounts, but says nothing about pending/unsettled funds, unknown-wallet behavior, or freshness of the figures.

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?

Two short sentences, front-loaded with the resource and its breakdown, with no filler. 'Free.' is terse and arguably useful, though it trails as a fragment rather than being integrated.

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?

This is a one-parameter read tool with no output schema, and the description states what the returned data consists of and that it costs nothing. Combined with annotations covering the read-only profile, that is enough for an agent to call it correctly; token units and units-of-account are the only minor omissions.

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 0%, so the description carries the burden, yet it only says 'a wallet' without explaining that the parameter is a 0x-prefixed hex address or what happens if the address is unknown. The regex pattern is self-evident in the schema, which limits the damage, but the description still compensates very little.

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 names a specific resource and its two components: what is owed to a wallet (winnings and refunds) versus what has already been paid. That distinguishes it clearly from siblings like play or send_usdc, though the verb is only implied by the title rather than stated in the description itself.

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 or when-not-to-use guidance and no mention of alternatives such as get_result for per-round detail. The single word 'Free' lightly nudges an agent toward calling it, but that is not real routing guidance.

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