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

With no annotations, the description carries full behavioral disclosure burden but only states the core check. It omits output format, error handling, IP version support, rate limits, or authentication needs, leaving the agent to guess.

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 front-loaded sentence with no wasted words. It efficiently communicates the action and resource in a clear, scannable format.

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?

Despite having an output schema and a single parameter, the description is incomplete for an agent selecting among many threat-intel siblings. It fails to mention what distinguishes this from 'feodo' or other C2 checkers, or any limitations or usage hints.

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 schema's 'q' parameter has zero description coverage, but the tool description explicitly implies it is an IP address by saying 'Is IP on...'. This adds critical semantic meaning, though it leaves IPv4/IPv6 format unspecified.

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 the tool checks if an IP is on the abuse.ch Feodo botnet C2 list, using a specific verb ('Is') and resource ('Feodo C2 List'). It does not, however, differentiate from the similarly named sibling 'feodo', so it lacks explicit distinction.

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 usage guidance is provided. The description does not mention when to use this tool over related threat-intelligence tools like 'feodo', 'botnet_tracker', or 'c2_infrastructure', nor does it offer any exclusions or alternative routing.

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