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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds substantial context beyond them: a per-call price ($0.01 USDC via x402), where the payment goes (_meta["x402/payment"]), that failed/invalid calls are not charged, and that results are unverified criminal claims with often-null country/sector. This is unusually rich behavioral disclosure.

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?

Front-loads purpose and filter scope before routing and cost details; every sentence carries distinct information. It is dense with several clauses in the final sentence, which slightly reduces readability but not substance.

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?

Covers purpose, alternative, data caveats, and billing for a 2-param read-only tool with no output schema. The only gap is that returned fields are not enumerated (country/sector nulls only hinted), which matters somewhat without an output schema.

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 coverage is 100%, so both parameters (group, limit) are already fully documented with examples and ranges in the schema. The description's 'akira or qilin' example and the 1-10 range merely restate schema content, so 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?

States a specific verb (list), resource (ransomware leak-site claims), and scope (newest 1-10, optional group filter). It explicitly distinguishes itself from the sibling lookup_victim, so an agent can route without opening either schema.

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?

Gives the when-to-use case (watch recent activity) and names the alternative tool (lookup_victim) with the condition that selects it (search for a specific company). Nothing is left to inference.

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