ransomwareGroups

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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is covered. The description usefully adds the data source (ransomware.live) and the shape of the payload, but says nothing about pagination behavior, rate limits, or how current the tracked-group list is. Adds some value above annotations, not rich 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?

Two tight sentences with zero padding; the operation and the return contents are front-loaded. Slightly more efficient than the norm, but nothing exceptional in structure.

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 compensates by naming the returned fields (names, descriptions, onion URLs, profile info), which is enough for an agent to know what it gets back. The only gap is that the 'all' framing obscures the default 100-item page size, a minor omission for a simple read.

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 description coverage is 100% (limit 1-200 default 100, offset for the cached response), so the schema fully documents both parameters. The description adds no paging guidance — notably it says 'List all' without noting the default 100-record cap — so baseline 3 is correct.

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?

Specific verb+resource: 'List all known ransomware groups tracked by ransomware.live', with a clear enumeration of returned fields. It implicitly separates itself from the singular ransomwareGroup sibling by being the bulk-list variant, but never names siblings explicitly, so it stops short of top marks.

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 when-to-use or when-not-to-use guidance. Critically, the sibling ransomlookGroups appears to be a near-identical 'list all groups' tool from a different provider, and the description never explains why an agent would pick one over the other. Nothing about prerequisites or result-set scope either.

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