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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the description need not repeat safety. It adds the 'immutable' property of the data and the 'Free' cost note, plus the fields returned. However, it omits pagination, ordering, or any indication of the response size or format, which would be useful context.

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?

A single sentence front-loads the key point ('Free' and 'Lists') and efficiently packs the response contents. No wasted words; the description is compact and immediately informative.

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 parameterless list tool with no output schema, the description adequately states what it returns (the fields). It does not mention pagination, limits, or ordering, but these may be less critical given the simple nature. The tool is likely to return all records; a mention of any maximum or sorting would be a minor enhancement.

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, so the schema is fully covered (100%) and the description does not need to explain arguments. The baseline of 4 applies; no additional parameter semantics are 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 clearly states the tool lists immutable recorded paid responses with specific fields (request, time, Base tx, sha256, verdict). This is a distinct verb-resource pair and differs from siblings like get_sample_report (which likely retrieves a single report) and the token safety checks.

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?

No explicit guidance on when to use this tool versus alternatives. It says 'Free' and lists contents, but does not mention get_sample_report as the option for retrieving a specific report, nor does it define any conditions for choosing this listing over other tools.

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