ransomwareGroups

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

No annotations present. Description mentions return fields but does not disclose limitations such as rate limits, data freshness, or authentication needs. Adequate for a read-only listing tool.

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 sentences clearly structured: first states purpose, second details returns. No extraneous information.

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, the description is complete: specifies it returns all known groups and key fields. No output schema, but description compensates adequately.

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?

Input schema has 0 parameters with 100% coverage. Description adds value by specifying the output (group names, descriptions, onion URLs, profile information) beyond the schema. Baseline 4 applies for 0 parameters.

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 clearly states 'List all known ransomware groups tracked by ransomware.live.' with specific verb (list), resource (ransomware groups), and source. Distinct from siblings like ransomwareGroup (single group) and 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?

Description implies usage for getting all groups but does not explicitly state when to use vs alternatives like ransomwareGroup or ransomwareSearch. No exclusions or prerequisites provided.

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