ip_reputation

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

With no annotations, description covers the key requirement (API key) and source (AbuseIPDB), but lacks details on rate limits, definition of 'malicious', or output behavior beyond what output schema might provide.

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?

Two concise sentences, front-loaded with action and resource, no unnecessary words.

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?

Simple tool with one parameter and output schema present, but description omits details like possible return values or error conditions, making it slightly incomplete.

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_address is implied by context but not explicitly described; schema coverage 0% means description should add meaning, but it only says 'IP address' without validation, format, or examples.

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 uses specific verb 'Check' and resource 'IP address is reported as malicious using AbuseIPDB', clearly distinguishing from sibling tools like cve_lookup or port_scan.

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?

States when to use (check IP reputation) and a prerequisite (ABUSEIPDB_API_KEY), but does not explicitly mention when not to use or alternatives.

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