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

With no annotations provided, the description carries the full burden of behavioral disclosure. 'Collect' implies an active network scan, but the description does not say what data is returned, that external DNS/WHOIS sources are queried, whether it can be slow or fail for dead domains, or whether rate limits apply.

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?

A single 10-word sentence, front-loaded with the main action and resource, with zero filler. Every word earns its place; the leanness is a strength even though brevity comes at the cost of other dimensions.

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 no annotations, no output schema, and an undefined scope term like 'public network intelligence', the description leaves real gaps: what the returned report contains, which sources are queried, and how it relates to overlapping siblings. It is a minimum-viable one-liner rather than a complete definition.

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 parameter has no description (0% schema description coverage), so the description must compensate. 'for a domain' confirms the parameter receives a domain name, but does not specify format constraints such as FQDN vs bare domain, whether subdomains are accepted, whether URLs must be stripped, or whether IPs are valid.

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 a specific verb ('collect'), a resource ('DNS records and public network intelligence'), and a target ('a domain'). However, the description does not differentiate it from the overlapping sibling get_dns_lookup, so an agent cannot fully distinguish the two tools from the text alone.

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 given on when to prefer this tool over alternatives like get_dns_lookup or post_domain_due_diligence, and no exclusions, preconditions, or decision criteria are stated. The phrase 'public network intelligence' only weakly implies a broader investigative tool than a raw DNS query.

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