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

Despite annotations already marking readOnlyHint=true and destructiveHint=false, the description adds substantial behavioral context: the v1.16.0 breaking change in vulns format, the two-tier cloud_provider detection logic, null-explicit field behavior, the meaning of tor_exit=false in relation to sources_unavailable, and conditional next_calls. This goes far beyond what annotations convey.

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 dense but well-organized, front-loading the core purpose and then layering important details like version changes, detection logic, and rate limits. It is a single large paragraph and could benefit from bullet points, but every sentence carries meaningful information without redundancy.

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 one parameter and a rich output schema, the description thoroughly explains the return fields, null-explicit behavior, edge cases (e.g., unknown CVEs, fetch failures), and conditional next_calls. It even clarifies tier-dependent reputation sources. No significant gaps remain.

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 single parameter 'ip' is fully described in the schema (100% coverage) with type and examples. The description adds no extra parameter-specific syntax or constraints, but since the schema already covers it, a baseline of 3 is appropriate.

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 opens with a specific verb+resource: 'Query comprehensive IP intelligence' and enumerates the exact data types (reverse DNS, ASN, ports, vulnerabilities, etc.), making its scope unmistakable. It also differentiates from the sibling tool threat_report by explicitly stating 'for orchestrated IP+reputation use threat_report,' and references next_calls to related lookups.

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?

It gives an explicit usage directive: 'Use for IP investigation; for orchestrated IP+reputation use threat_report,' naming the alternative tool. It further clarifies tier-based behavior (Free vs Pro) and rate limits, helping the agent decide when and how to invoke it.

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