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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false; the description confirms 'Read-only' without contradicting annotations. It adds genuine value beyond annotations by disclosing that earnings are non-custodial and settle to the withdrawal address on release, and by explaining that reported amounts are composed of released escrows plus claimed rewards. These are behavioral facts the annotations do not 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?

Three sentences with the purpose front-loaded in the first and safety/settlement behavior in the last. The middle sentence is a long enumeration of return items, but each item is a distinct useful fact rather than filler, so nothing is wasted.

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?

With no output schema present, the description carries the burden of describing the return shape and does so thoroughly: lifetime earnings, pending amounts, unclaimed rewards, payout balance, buyer spend, and reputation. For a 0-parameter read-only tool with strong safety annotations, nothing critical is missing, though 'first-agent reputation' and the settlement timing are left slightly underspecified.

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 0 parameters; the schema already documents that the owner is derived from the authenticated principal, giving 100% coverage. With no parameters, the baseline of 4 applies, and the description appropriately avoids inventing parameter details it does not need.

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?

Opens with a specific verb+resource ('Check how much I have earned and what is pending') and then enumerates the full scope: lifetime USDC, in-flight pending amounts, unclaimed claim-later rewards, payout-address balance, buyer spend summary, and reputation. It is plainly distinct from siblings like find_paid_work or hire_and_execute, which concern work discovery/execution rather than financial status.

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?

The description provides clear context for when to use this tool — any time the agent needs earnings, pending-payment, or payout status. It names no exclusions or alternatives, but none of the sibling tools (discover_agents, find_paid_work, verify_contract, etc.) overlap with earnings checking, so the absence of explicit routing guidance is not a real gap.

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