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

Annotations already establish readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds genuine context beyond that: it enumerates the balance states returned, and clarifies that identity verification and payout details are configured elsewhere on the outreach dashboard while this tool only reports whether they are missing. That 'reports but cannot fix' boundary is the useful behavioral disclosure.

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 what the agent gets back, followed by the prerequisite/verification caveat. The parenthetical list of balance states is dense but each item is informative; there is no filler or restatement of the title.

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?

For a zero-argument read tool with an output schema, the description covers the meaningful gaps: what is returned (balances, ledger, eligibility) and the one non-obvious behavior (it only surfaces missing verification/payout setup). Nothing an agent needs to call it correctly is 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?

The tool takes zero parameters, so the baseline is 4. The description correctly describes only output content and makes no claims about inputs, leaving nothing misrepresented.

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 the concrete content of the resource: balances across four states, the commission/payout ledger, and payout eligibility. It implicitly distinguishes itself from the write-side sibling ambassador.earnings.request_payout by framing its role as 'whether a payout can be requested', but it never names that sibling or states a verb explicitly, so differentiation requires inference.

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 is the pre-flight read before ambassador.earnings.request_payout, and that it reports missing verification/payout details. There is no explicit statement of when to call this versus the withdrawal/request tools, and no stated exclusions.

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