whois_lookup

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

With no annotations, the description should disclose behavioral traits like rate limits, data sources, or caching. Instead, it only states 'Perform WHOIS lookup', leaving the agent unaware of potential limitations or side effects.

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 very concise (one sentence) but lacks structure such as separate sections for usage, behavior, or examples. While no words are wasted, the minimalism sacrifices helpfulness.

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 presence of an output schema (not shown), the description could be considered minimally adequate for a simple lookup. However, it does not explain what data is returned or how to interpret results, and sibling tools suggest a broader recon context that remains unaddressed.

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's domain parameter is a plain string with no description. The tool's description does not add any extra meaning, such as required format (e.g., example.com) or accepted value types. Schema description coverage is 0%, so the description should compensate but fails.

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 verb 'Perform' and the resource 'WHOIS lookup for a domain'. It distinguishes from sibling tools like dns_enumeration and ip_reputation by focusing on domain registration data.

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?

No guidance is provided on when to use this tool versus alternatives such as dns_enumeration or full_recon. The description lacks context for appropriate usage scenarios.

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