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

No annotations are present, so the description must disclose behavior. It only mentions that it provides RDAP structured data, but does not describe network behavior, rate limits, error handling, or what the response includes. As a data lookup tool, it likely performs a read-only network request, but this is not stated.

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 brief, but it is under-specified rather than concise. It is a single fragment that does not include essential details about the input or behavior, so it fails to earn its place as an effective description.

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 annotations, no parameter description, and a vague description, the tool is inadequately specified. Although an output schema exists, the description does not reference it or explain what the agent will receive, leaving critical information missing for correct invocation.

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 has one parameter 'q' with 0% description coverage, and the description does not explain what 'q' represents (presumably a domain name). The agent cannot infer the expected format or semantics from the description alone.

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 resource (RDAP domain) and that it returns structured registration data, but lacks a clear verb like 'lookup' or 'get'. It also does not differentiate from sibling tools 'rdap' and 'rdapip', making it ambiguous which specific functionality is intended.

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 'whois', 'rdap', or 'rdapip'. The description gives no context about the intended use case or when RDAP is preferred over other lookup methods.

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