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

With no annotations provided, the description carries the burden of disclosing behavior. It does list what data is returned (DNS, WHOIS, etc.), but it does not mention any side effects, authorization requirements, rate limits, or limitations. The core function is clear, but behavioral depth is minimal.

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, concise sentence that front-loads the key concept ('Domain intelligence') and then enumerates the main data types. It is efficient and free of wasted words, though slightly terse in its omission of context.

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 simple one-parameter tool with no output schema, the description provides a useful summary of the return content. However, it lacks information about the response format, whether all listed fields are always included, and any error conditions. It is adequate but has clear gaps in completeness.

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 100% coverage for the single parameter 'domain', including an example. The description itself adds no further parameter-specific meaning, so it does not exceed what the schema already provides. Baseline 3 is appropriate.

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 identifies the tool as providing domain intelligence, listing specific data categories (DNS, WHOIS, email patterns, LinkedIn/XING profile). This distinguishes it from sibling tools focused on companies, people, or health checks, though it lacks an explicit verb like 'retrieve' or '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 no guidance on when to use this tool versus alternatives. For example, it mentions 'email patterns' which overlaps with the sibling 'email_finder', but the description does not clarify how they differ or when one should be chosen over the other.

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