netintel_domain_report

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

With no annotations, the description carries the full behavioral burden. It does disclose the key trait that everything is aggregated into 'one call' versus assembling sub-tools, and that output is risk-scored, but it says nothing about read-only safety, latency/cost of the multi-source aggregation, failure modes when a source is unavailable, or rate limits.

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 content is a single front-loaded sentence leading with the strongest hook ('One call returns...'), with no filler. However, the trailing ellipsis indicates the text is truncated, so the description is cut off rather than deliberately tight.

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?

There is no output schema and no annotations, so the description is the only source of return-value and behavior information. It lists the report's sections, which is genuinely useful, but the truncation ('…') and the absence of any guidance on the domain input format or comparison to sibling report tools leave it only marginally complete for a complex aggregation tool.

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?

Schema description coverage is 0% and the single 'domain' parameter has no description in the schema. The description only restates 'for a domain' and adds no format detail (protocol prefix, subdomain handling, IDN), so it does not compensate for the coverage gap. Only the trivial single-param nature keeps this from a 1.

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?

States a specific verb and resource ('returns a complete intelligence profile for a domain') and enumerates the aggregated contents (WHOIS, DNS, SSL, tech stack, blacklist) plus the output form (risk-scored report). It fails to distinguish itself from heavily overlapping siblings like netintel_domain_report_full, netintel_domain_vet, and netintel_domain_due_diligence, so it lands at 4 rather than 5.

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 clause 'so agents can fully vet a domain' implies the intended use case (comprehensive one-shot vetting), but there is no explicit when-to-use, when-not-to-use, or named alternative despite many sibling tools covering the same sub-tasks. Usage is implied rather than directed.

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