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

With no annotations, the description carries the full burden of behavioral disclosure. It implies a read-only lookup by mentioning returned fields, but it does not explicitly state that there are no side effects, nor does it mention any requirements or limitations such as authentication, freshness, or scope of data.

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 description is only two sentences and every part contributes: the first states what data is available, and the second tells when to use it. However, some phrasing is jargon-heavy ('Public proof filers got paid') and could be clearer without adding length.

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?

The description names the key return fields, which helps, but there is no output schema and no explanation of the output shape or units. Terms like 'Public proof filers' and 'filing is worthless' are left undefined, so an agent may struggle to interpret the result precisely.

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 input schema is an empty object with 100% coverage and zero parameters, so there are no parameter semantics to explain. The baseline of 4 is appropriate because no additional parameter documentation 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 identifies the resource as earnings for public proof filers and names the specific data provided: recent filerPayoutTxUrl and earnedUsdOnChain. It does not use an explicit verb like 'get' or 'check', but the meaning is clear enough to distinguish it from siblings like file, status, or unlock.

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?

The second sentence provides clear usage context: read this before deciding whether filing is worthless. It does not name alternatives or explicitly say when not to use it, but the purpose is sufficiently scoped.

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