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

Annotations only declare readOnlyHint and openWorldHint; the description adds substantial behavior the annotations cannot convey: a $12 USDC charge, x402 payment via _meta, optional sk_scrapling_/sdp_ key auth, and payload contents (as_of stamps, freeze flags, SHA-256 checksum). The only gap is that delivery format and data volume, which matter when an agent commits $12, are unstated.

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?

Two dense sentences with zero filler, and the price/payment constraint is front-loaded before the payload description. The address-type list is a long compound but each item is informative rather than redundant.

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 output schema, the description carries the burden of describing the return, and it does so only partially: it names attributes (as_of, freeze flags, checksum) but not the file format, record count, or how the download is delivered. For a paid, zero-required-parameter purchase tool, that omission leaves a meaningful unknown before committing funds.

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?

There is a single optional api_key parameter and the schema already documents it at 100% coverage, including the sk_scrapling_/sdp_ prefixes and the x402 fallback. The description reinforces the payment model with 'PAID $12 USDC' but adds no parameter-level detail beyond what the schema states, 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 description gives a specific verb and a precisely enumerated resource set: 'Download every labeled hacker/exploit, scam/phishing, sanctioned and mixer address plus live hack-tracker attributed wallets.' It also implicitly distinguishes itself from the pass-based siblings by stating it is premium pay-per-download, so an agent can tell it apart from pass_day/pass_month and the free_* lookups.

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?

It usefully excludes one alternative class by saying the bundle is 'NOT covered by day/month passes', which is real routing information. However, it never points to the obvious alternatives for sampling or single-record lookups (preview_dataset, list_datasets, free_datasets, hack_tracker), so an agent still has to infer that this is the bulk/premium path and the others are the cheap checks.

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