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

With no annotations, the description carries the full burden of behavioral disclosure. It implies a network lookup by mentioning WHOIS/RDAP but does not explicitly state read-only behavior, rate limits, or potential side effects. The listed output categories give some context, but key behavioral traits are left to inference.

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?

The description is a single, punchy phrase that front-loads the tool's purpose and core output categories. It contains no redundant words or filler, making it concise. However, it is structured as a fragment rather than a complete sentence, slightly reducing clarity.

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 the tool's simplicity and the presence of an output schema, return values are covered. But the description fails to explain the query parameter format, distinguish this tool from similar siblings, or state any usage constraints. With many related tools and zero schema descriptions, the context is notably 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?

The input schema provides a single 'q' parameter with no description (0% coverage). The tool description does not explicitly explain what 'q' should contain (e.g., IPv4/IPv6 address, domain name), only inferring from 'IP WHOIS' that it is an IP query. This is insufficient to fully compensate for the schema's lack of descriptions.

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 clearly states the tool performs IP WHOIS / RDAP lookups and specifies the types of data returned (network owner, range, abuse contact). However, it does not differentiate it from closely related siblings such as 'whois', 'rdap', 'rdapip', or 'ripewhois', which likely serve similar overlapping purposes.

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 description provides no guidance on when to use this tool versus alternatives. It does not mention whether it is specifically for IP addresses, when to prefer 'whois' for domain lookups, or any criteria for choosing among the many similar sibling tools. No exclusions or alternatives are noted.

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