IP network owner

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so safety is covered structurally. The description adds genuinely new context: the upstream data source is the RIR via RDAP and no API key is required, which tells the agent the call is free of credential prerequisites. It does not mention behaviour for private/invalid IPs or rate limits, keeping it below a 5.

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 dense sentences with the payload contents front-loaded and no filler; the source and key requirement are packed into trailing clauses. Nothing needs trimming.

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?

With no output schema, the description usefully enumerates the returned fields (organisation, range, country, abuse contact), which covers the return-value burden. But it leaves the second parameter unexplained and says nothing about response shape for private IPs or lookup failures, so it is only minimally sufficient.

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 description coverage is 0% for both parameters. The description does constrain ip_address indirectly by saying "public IP" and framing it as an IP found elsewhere. However, investigation_id is completely undocumented in both schema and description, and no format examples (IPv4 vs IPv6) are given, so the description only partially compensates for the coverage gap.

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 states exactly what is retrieved — the network registration record for a public IP (organisation, range, country, abuse contact) — and names the source (regional internet registry over RDAP). That source framing distinguishes it from reputation siblings like abuseipdb_check and virustotal_check, which report maliciousness rather than registration ownership.

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?

"Already run for an IP target; use it for other IPs you find" tells the agent this is a follow-on enrichment step for newly discovered IPs rather than the primary target. It gives clear context but never names an explicit alternative or exclusion condition, so the agent must infer when a different IP tool is the better choice.

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