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

Annotations already cover read-only, idempotent, non-destructive, closed-world, so the bar is lower, but the description adds real context beyond them: visibility is restricted to opted-in operators, receipts are private by default, and an empty list is a legitimate outcome. It also removes payment ambiguity by stating the call is free and requires no x402 challenge — unusual and valuable operational detail.

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?

Purpose is front-loaded in the first sentence and the empty-list caveat follows in logical order. The payment sentence is somewhat redundant, saying "FREE — no payment required", "call directly without payment", and "this tool is free" in one breath, which is more repetition than the point needs.

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 tool with full annotation coverage and no output schema, the description covers purpose, visibility scope, empty-result meaning, and cost model. The one gap is that it never says what a receipt record actually contains, which an agent must guess since no output schema exists.

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 zero parameters and the description correctly says nothing about inputs, which is the right baseline of 4. The only input-adjacent information is that settlement scope is fixed to opted-in operators, which is scope rather than parameter semantics.

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?

States a specific verb+resource ("Read settlement receipts") plus a meaningful scope qualifier ("OPTED-IN operators only"), which an agent can act on. It does not explicitly name a sibling such as commons_set_receipts_opt_in or commons_list_operators, so the routing is inferable rather than spelled out.

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?

"Receipts are private by default; an empty list is an honest answer" usefully tells the agent not to treat an empty result as an error or retry. However, there is no explicit statement of when to prefer this over adjacent commons tools (operator reputation, aggregates, changes) and no prerequisites for opting in beyond the implicit mention.

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