IP Reputation

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

With no annotations, the description carries the full burden, and it discloses two genuinely useful behavioral facts: the required GREYNOISE_API_KEY / ABUSEIPDB_API_KEY env vars and the graceful degradation to available:false instead of an error when a key is absent. It does not cover rate limits, caching, or response shape, so it is strong but not complete.

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 tight sentences, front-loaded with what is checked and followed immediately by the operational caveat. Every clause carries information and nothing is padded.

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 single-parameter lookup with no annotations or output schema, the description covers the data sources, the auth requirement, and the partial-failure behavior, which is most of what an agent needs. It leaves IP format expectations and returned fields unaddressed, though the latter is largely excused by the absence of an output schema.

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?

There is one parameter, ip, at 0% schema description coverage, so the description must compensate and it does not — it says only 'for an IP' with no IPv4/IPv6 format guidance or handling of invalid input. The parameter name is self-explanatory but the description adds nothing beyond it.

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?

States a specific verb (checks) and resource (IP reputation) and names the two upstream data sources — GreyNoise scanning noise and AbuseIPDB abuse reports — which implicitly separates it from rdap_lookup and traffic_by_ip. It stops short of explicitly naming or contrasting with those siblings, so it is clear but not fully differentiated.

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 purpose implies the context (reputation/abuse screening for an IP), but there is no explicit when-to-use or when-not-to-use guidance relative to neighbors such as get_ip_context or rdap_lookup. Usage must be inferred from the named sources.

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