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

Annotations already declare it non-read-only, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds real value beyond them by defining the amount affected (everything withdrawable) and the account-state prerequisites, which annotations cannot convey.

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 tight sentences with the action front-loaded and the preconditions trailing. Every clause carries information: scope, destination, and three requirements; nothing 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, and annotations cover the mutation/idempotency profile. What remains for an agent to know before invoking  scope, destination, and preconditions  is fully present.

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 no parameter syntax or meaning for the description to supply; baseline 4 applies. The description correctly redirects the target configuration (payout details) to the dashboard rather than to an argument.

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?

States a specific verb+resource ("Request a payout") and narrows scope to "everything withdrawable, to the payout details saved on the outreach dashboard." An agent can distinguish it from host.earnings.withdraw by the ambassador/outreach framing, though no sibling is named explicitly.

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?

Gives concrete gating conditions for successful use: identity verified, payout details set once on the dashboard, and at least the minimum confirmed. It does not name an alternative tool (e.g., host.earnings.withdraw) or state when not to use it, so it is clear context without explicit routing.

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