Bulk IP Threat Intelligence Lookup

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false. The description adds value by detailing the response content (threat scores, VPN/proxy/Tor/bot detection, etc.), which is beyond what annotations provide. There is no contradiction.

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 composed of two efficient sentences. Every sentence adds value: the first states the core function and limit, the second describes the output shape. No fluff or repetition.

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?

Given the tool's complexity (up to 50k IPs, many detection types) and the lack of an output schema, the description sufficiently explains the return format. It could note that results are per IP, but that is implied. The annotations cover safety and idempotency, so no further behavioral cues are needed.

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 coverage is 100% and includes descriptions for all three parameters. The description adds context by summarizing the output fields (threat scores plus detections), which helps the agent understand what the tool returns. Baseline 3 is elevated to 4 because the description provides meaningful extra information 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 the tool's purpose: 'IP threat intelligence for up to 50,000 IP addresses in one request'. It specifies the verb (lookup), resource (IPs), and scale (bulk). This differentiates it from the sibling tool 'ip_security_lookup' which likely handles single IPs.

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 implies bulk usage ('up to 50,000 IP addresses') but does not explicitly state when to use this tool versus alternatives like 'ip_security_lookup'. No when-not-to-use or exclusion criteria are provided.

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