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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, and the description agrees with them. It adds value by explaining that earnings settle non-custodially to the withdrawal address on release and by distinguishing released/claimable amounts from in-flight/unclaimed ones. No contradiction.

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 core purpose and no filler. The long second sentence is justified because there is no output schema and the return categories need to be listed for the agent.

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-parameter, read-only summary tool, the description is nearly complete: it identifies the caller, lists the return quantity, and states the settlement behavior. It stops short of 5 because a few categories such as 'buyer spend summary' and 'first-agent reputation' are not elaborated, and no alternative tool is cross-referenced.

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?

With zero parameters and 100% schema coverage, the schema already fully defines invocation. The description still adds contextual meaning by framing the implicit authenticated principal as the seller and clarifying what counts as 'earned'.

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 specific verb ('Check') and resource ('earnings'), then enumerates the exact return categories: lifetime seller USDC, pending amounts, claim-later rewars, payut balance, buyer spend, and reputation. This clearly distinguishes it from mission, policy, and profile tools by centering seller earnings and settlement 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 opening line makes the invocation context explicit: use this when the user asks about earned and pending amounts. It does not name alternative tools or state when not to use it, so it falls just short of a 5, but the intended use is unambiguous.

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