search_abuseipdb

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

Describes return values, warning behavior above 50% score, and passive nature. With no annotations, description carries full burden; it is mostly transparent but omits details like rate limits or error handling.

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?

Four sentences, each adds unique value: purpose, returns, warning, prerequisites, authorization. No redundancy, front-loaded.

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?

Covers all essential aspects for a simple 2-parameter tool with no output schema: purpose, return data, warning, prerequisites, and usage authorization. Agent can use correctly.

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 50% with only json_output described. Description adds meaning for the ip parameter implicitly but does not specify format or constraints. Baseline 3 due to partial compensation.

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?

Clearly states it checks an IP address against AbuseIPDB for abuse reputation, specifying key returned data. Distinguishes from sibling IP tools by naming the specific source and data returned.

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 mentions required API key environment variable and authorized use conditions. Does not list alternatives or when not to use, but context from sibling tools provides differentiation.

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