x402_list_earnings

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states 'View' (implying read-only) but does not mention authentication requirements, data aggregation details, rate limits, or that it shows the caller's own revenue. This leaves significant ambiguity about the operation's side effects and constraints.

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?

The description is two sentences, front-loads the primary purpose, and then efficiently summarizes output categories. No filler or redundant phrasing.

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?

The description covers the core purpose and output types, which is adequate for a simple read-only listing tool. However, without annotations or an output schema, it omits critical behavioral context like whether the operation is read-only, any authentication needs, or how the data is aggregated, leaving some gaps in context.

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 description adds meaning to the 'groupBy' parameter by listing the categories 'endpoint, top payers, and revenue over time,' which directly correspond to the enum values (endpoint, payer, time). This gives the agent semantic context beyond the schema's generic descriptions, while 'limit' and 'period' remain adequately documented by the 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 clearly states the tool's function with a specific verb ('View') and resource ('your x402 payment revenue'), and further elaborates on the output dimensions (earnings by endpoint, top payers, revenue over time). This distinguishes it from sibling x402 tools like x402_tx_status (status) or x402_send (payments).

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?

No guidance is provided on when to use this tool versus alternatives. For example, it does not contrast with x402_balance or x402_yield, which could also relate to earnings. Lacks any mention of prerequisites or typical use cases, giving the agent no decision support.

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