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 lists returned data categories but does not explain whether it queries RDAP or WHOIS, handles errors, follows redirects, or has rate limits. It adds minimal behavioral context beyond the title.

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 extremely short and to the point, with no redundant words. It is a single line that efficiently communicates the general scope. However, it is so brief that it sacrifices necessary information, so while conciseness is good, the structure is minimal.

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 tool with one undocumented parameter and no annotations, the description is far from complete. It does not explain input, output, or failure modes. Despite having an output schema, the description adds no context about how to use the tool correctly, making it inadequate for an agent to call it effectively.

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 has one parameter 'q' with 0% description coverage. The description never explains what 'q' represents (domain, IP, ASN?) or its format. Since the schema provides no semantics and the description offers none, an agent cannot correctly populate the parameter.

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 the tool covers WHOIS/RDAP data and lists categories like registration, status, nameservers, and DNSSEC. It gives a clear domain of operation but is vague about the exact action (lookup? query?) and does not distinguish it from siblings like rdap, whois_check, or ripewhois. It is more than a tautology but lacks specificity.

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?

There is no guidance on when to use this tool versus alternatives. No mention of prerequisites, input format, or conditions. The description is a bare statement of scope with no context about appropriate use cases.

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