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

With no annotations, the description carries the full burden, and it does so thoroughly: it declares 'Read-only operation — no side effects, no parameters,' describes the data source as 'real_blockchain,' discloses the 100-row limit, and explains the x402 HTTP 402 payment challenge with exact USDC amount and receiver.

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?

Every sentence earns its place: safety/no-params, return payload detail, usage routing, and payment mechanism. It is front-loaded with the most critical call-time facts and avoids filler.

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 tool with no output schema and no annotations, the description is fully self-sufficient: it covers the return shape, data provenance, limits, wallet/market context, cost, and sibling routing. Nothing needed to invoke it correctly is missing.

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 has zero parameters, which earns the baseline of 4. The description explicitly confirms 'no parameters,' consistent with the empty input schema and 100% schema coverage.

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 and resource: it returns the real on-chain payment history to this service's fee receiver on Base. It lists the exact fields returned and explicitly distinguishes itself from siblings by naming what get_market_stats and get_bot_status are for.

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?

It gives an explicit when-to-use condition: 'Use it when you need provable revenue or settlement evidence.' It also names the alternatives and their purposes, so an agent can choose correctly without inference.

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