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

Annotations already declare non-read-only, idempotent, non-destructive, closed-world. The description adds real context beyond them: the call sweeps the full withdrawable balance (not a partial amount), funds go to the portal-saved payout details, and three gating conditions must hold. It does not say what happens when those conditions fail, which keeps it short of a 5.

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 sentences, front-loaded with the action and scope, followed by prerequisites. No filler, no repetition of the title, and nothing that could be cut without losing 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?

An output schema exists so return values need not be described, and the prerequisites plus payout destination cover what an agent needs to decide and invoke. Minor gap: no statement of the failure mode or error when identity/payout details/minimum are not met.

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?

Zero parameters, so the baseline is 4, and the description usefully explains the absence of an amount parameter by stating it withdraws 'everything the venue can withdraw' — an all-or-nothing semantic that an agent could not infer from an empty schema.

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 gives a specific verb ('request a payout') and resource ('everything the venue can withdraw') plus the destination (saved payout details). It is clearly distinguishable from the read-only host.earnings.wallet, though it does not name a sibling explicitly the way a top-tier definition would.

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?

It states the preconditions for use: identity verified, payout details set on the portal, and at least the minimum withdrawable balance. That is solid context, but there is no explicit when-not-to-use guidance or named alternative (e.g. vs. ambassador.earnings.request_payout).

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