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

Annotations already establish readOnlyHint=true and destructiveHint=false, so the bar is lower. The description adds meaningful extras: public access with no auth, privacy behavior ('Addresses and signatures only, never identities'), and settlement timing for carrier payouts. This goes beyond the structured annotations without contradicting them.

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 core claim is front-loaded ('full payout ledger in one read') and every clause adds a distinct content category or constraint. It is dense and slightly run-on, but the parentheticals carry real information rather than padding.

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 tool with no output schema, the description is unusually complete: it lists data categories, clarifies what is and isn't included, states auth requirements, and even gives the REST twin URL. An agent has enough to decide whether and how to invoke it.

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 and the schema fully covers that empty contract, so the baseline is 4. The description introduces no parameter ambiguity and correctly signals that the tool needs no inputs.

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 uses a specific, observable scope: 'The platform's full payout ledger in one read' and then enumerates the exact categories (carrier payouts, leaderboard purse, raid bounties, revenue side, retention metrics). It clearly distinguishes this from generic stats or leaderboard siblings by spelling out what content is included.

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 implies when to call the tool — whenever a complete payout/revenue/retention picture is needed — and adds 'Public, no auth' as access context. However, it never names alternatives or states when not to use it, such as preferring adnet_stats, page_leaderboard, or bounty_list for narrower questions.

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