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 add real behavioral context: sorting/paging are server-side, the table grows without bound (unlike other per-match data that is purged), and `total` is returned per page. It doesn't state auth requirements, rate limits, or confirm read-only semantics, so gaps remain.

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?

It is front-loaded with the core definition, but the middle sentences are editorial ('A claim about where the money went that costs money to check is not a claim anybody should believe') and don't help an agent select or invoke the tool. The unbounded-table rationale is justified; the philosophy is not.

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?

An output schema exists, so return values need not be explained, and 83% param coverage plus the server-paging/unbounded-growth notes cover the practical calling concerns. What's missing (sibling disambiguation, auth) is minor given the schema and output schema carry the rest.

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?

Schema description coverage is 83%, so the schema already documents npub, page, sort_col, sort_dir, and page_size. The description adds no per-parameter meaning (sort keys, direction, page-size semantics) beyond what the schema provides, so the baseline 3 applies.

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 opening line 'What every settled match paid, and to whom' names a specific resource and scope of data, making clear this is a settlement-history read. However, the verb (list/retrieve) is only implied, and there's no differentiation from near-sibling tools like beesknees_payout_history or beesknees_account_statement.

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?

There's no explicit when-to-use guidance or routing to alternatives, despite siblings (payout_history, account_statement) that could plausibly overlap. The 'Free on purpose' line hints at a cost/reason dynamic but doesn't help the agent select this tool over another.

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