whois_lookup

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

With no annotations present, the description carries the full burden and provides valuable behavioral notes: it uses python-whois (no subprocess/security benefit), warns about rate limits, and requires the target to be in allowed_hosts. These go beyond basic safety and give practical operational transparency.

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 appropriately sized and well-structured with Args, Returns, and Notes sections. It avoids fluff while including essential operational details. Slightly verbose due to the Notes, but every sentence adds value.

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 one-parameter tool with no output schema provided, the description covers the return data, input format, prerequisites, and practical caveats. It is complete enough for an agent to use correctly, though a brief note on failure behavior would make it fully comprehensive.

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 schema only defines 'target' as a string with no description. The description fully compensates by defining it as 'Domain name (e.g. "example.com") or IP address' and adds the allowed_hosts constraint. Given 0% schema coverage, this is excellent 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?

The description clearly states 'Perform a WHOIS lookup for a domain or IP address' with a specific verb and resource. It further details the information retrieved (registrar, dates, nameservers, contacts), which distinguishes it from sibling tools like dns_enumerate or shodan_lookup.

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 gives clear context for usage: when you need registration data for a domain or IP. It also notes rate-limiting and the allowed_hosts prerequisite. However, it does not explicitly compare to alternatives or state when not to use this tool, but the context is sufficiently clear for a simple tool.

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