Generate C2 Blocklist

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

The description adds value beyond annotations by specifying the output formats ('Returns CIDR list, hosts file, or plain IP list') and the subscription requirement. It does not contradict the readOnlyHint or other annotations, and provides useful operational 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?

The description is two sentences with no wasted words. It front-loads the core purpose and then lists key filters and outputs efficiently.

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 tool with three optional parameters and no output schema, the description covers all key aspects: purpose, filters, output format options, and a usage requirement (tier). No gaps are apparent.

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?

All three parameters (format, framework, since_days) have 100% schema description coverage. The description reinforces their purpose ('Filter by framework', 'recency window') but does not add new semantic detail beyond the schema.

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 clearly states 'Generate a firewall-ready C2 IOC blocklist from active beacons', specifying a concrete verb and resource. It distinguishes from sibling tools like search_detections or get_threat_intelligence by focusing on blocklist generation.

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?

The description mentions the required 'Purple tier ($11.99/mo)' as a prerequisite, and provides filtering criteria (framework, recency, format). However, it does not explicitly discuss when not to use this tool or compare to alternatives, though siblings are sufficiently distinct.

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