ransomwareGroups

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

No annotations are provided, so the description carries the burden. It states the basic read behavior and what is returned, satisfying the minimum for a simple list operation. However, it does not disclose potential rate limits, data freshness, or any edge-case behavior, which would be needed for a higher score.

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 a single sentence of roughly 20 words, front-loaded with the core action. It contains no filler or redundant information, earning full marks for conciseness and 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?

For a zero-parameter list tool with no output schema, the description adequately states the returned data fields and source. It does not mention how this tool relates to similarly named tools or any pagination, but those are less critical given the tool's simplicity.

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 accepts zero parameters, and the schema is empty. The baseline for zero parameters is 4, and the description correctly clarifies the scope ('all known') without needing to document any arguments.

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?

Description uses a specific verb 'List' and identifies a clear resource: 'all known ransomware groups tracked by ransomware.live.' It also details return fields (group names, descriptions, onion URLs, profile information), distinctly separating it from singular sibling tools like 'ransomwareGroup' or 'ransomwareGroupVictims.'

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?

Usage is implied ('call this to list all groups'), but the description gives no explicit guidance on when to prefer this over siblings like ransomwareRecent, ransomwareSearch, or ransomwareGroup. No alternatives or exclusions are mentioned.

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