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

With no annotations, the description carries the full behavioral burden for a financial mutation. It discloses the two outcome modes, which is useful, but says nothing about irreversibility, whether the claim can be repeated, authorization requirements, or what happens when the match is unresolved.

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 front-loaded sentence with zero filler and the two outcomes presented side by side. Nothing in it is redundant.

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?

An output schema exists, so return values need not be described, but for a prize-claiming money operation with no annotations and one undocumented parameter the description is too thin. Prerequisites, irreversibility, and failure modes are all absent.

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 75%, so the schema already documents npub, choice, and match_id. The description reinforces the choice semantics ('credit' vs 'charity' maps to 'keep' vs 'donate') but adds no format or constraint detail, and leaves dpop_token entirely undocumented in both places.

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 states a concrete action ('take the winner's share') with two explicit outcomes (credit or charity), so an agent knows what the tool accomplishes. It does not, however, name or distinguish itself from close siblings such as beesknees_pay_charity or beesknees_payout, so the differentiation burden falls entirely on the name.

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?

Usage is only implied: an agent can infer this applies after winning a match, and the description frames the keep-vs-donate fork. There is no explicit precondition (e.g., the match must be settled), no statement that it is one-shot, and no routing advice against the payout/charity siblings.

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