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

No annotations are supplied, so the description carries the full behavioral burden, yet it discloses nothing about whether the call is read-only, what permissions or auth are required, whether payment data is scoped to the caller, or what shape the response takes. The phrase 'got paid on-chain' only faintly hints at historical payout data and provides no 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?

The text is short, but it is a fragment rather than a structured statement of purpose, and its brevity stems from under-specification rather than economy. There is no front-loaded verb to orient the reader.

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?

With no annotations and no output schema, the description is the only source of information about this tool, and it says almost nothing. For a zero-parameter retrieval tool, an agent still needs to know what it returns and whether it is a safe read; neither is conveyed.

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, so there is nothing for the description to disambiguate beyond the empty schema; baseline 4 applies. The description adds no parameter meaning, but none is needed.

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 reads as a statement of fact ("Public proof filers got paid on-chain") rather than a description of an operation. It never states a verb like 'list' or 'retrieve' or what resource is returned, so an agent cannot tell whether this fetches payment records, checks eligibility, or reports totals, nor how it differs from siblings such as 'status' or 'discover'.

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 is no when-to-use guidance, no prerequisites, and no mention of any alternative tool or condition that selects this one over its siblings. The agent is left to guess entirely from the name.

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