threat_report

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

Discloses beyond annotations: rate limits (100/hr, 1000/hr for Pro), breaking change in enrichment.vulns format, and ASN prefix limitation. Annotations readonly etc. are consistent.

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?

Front-loaded with purpose and key details. Some extra details on version changes could be more concise but overall well-structured.

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 single parameter, annotations, output schema, and thorough description covering usage, limitations, and version history, the tool is fully described.

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?

Only parameter 'ip' is well-described in schema (type, format, rejection of private IPs). Description adds context but schema coverage is 100%, so baseline 3.

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?

Description clearly states 'Query comprehensive threat profile for an IP' and lists specific data sources (Shodan, AbuseIPDB, ASN/geolocation, open ports). It also distinguishes from sibling tool 'domain_report' for domain data.

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?

Explicitly states 'Use for IP investigation and SOC alert triage' and provides alternative 'for domain data use domain_report'. Also includes version-specific behavioral notes.

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