check_ips

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

With no annotations, the description carries the full burden. It discloses rate limits (50/day for free tier) and the batch nature, but does not mention idempotency, error behavior, or whether the tool is read-only. This leaves gaps in the agent's understanding of side effects.

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, each earning its place: the first states the action and target, the second provides a use case and a critical constraint (rate limits). No redundancy or excess.

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?

The tool has 1 parameter with full schema coverage, but no output schema. The description does not explain what the tool returns (e.g., risk scores, noise classification), which is essential for an agent to interpret results. It also lacks authentication requirements or explicit differentiation from 'check_ip', leaving the agent slightly under-informed.

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 description coverage is 100%, so the baseline is 3. The description adds no new information about the 'ips' parameter beyond what the schema already provides (array of strings, max 10, min 1). It does not clarify IP format or validation rules.

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 verb 'Check' and the resource 'multiple IP addresses against GreyNoise'. It also distinguishes itself from the sibling tool 'check_ip' by emphasizing batch capability ('in one call'), leaving no ambiguity about its purpose.

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 provides clear context: 'useful for triaging a list of suspicious IPs from logs or alerts.' It also mentions rate limits. While it does not explicitly contrast with 'check_ip' or state when not to use it, the use case is well-defined and implicitly differentiates from a single-IP check.

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