netintel_domain_report_full

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

With no annotations, the description carries full behavioral burden. It does usefully disclose that sections run concurrently and degrade gracefully on partial failure, which tells the agent to expect partial results rather than a hard error. It says nothing about auth requirements, latency, rate limits, or what the 'premium' label actually costs in quota, which matters for a call that fans out to six sub-services.

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 front-loaded sentence that leads with the core value proposition and then enumerates the sections; no filler. It is cut off with a trailing ellipsis, and 'premium' is unquantified marketing language, but the structure is efficient.

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 one-param aggregation tool with no annotations and no output schema, the description covers scope and partial-failure behavior but omits cost/quota implications of the 'premium' framing, parameter format expectations, and any hint of the response shape or timing.

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?

There is a single required 'domain' parameter with 0% schema description coverage, so the schema adds nothing. The description names the input implicitly ('domain profile') but never states accepted formats — root domain only, subdomains, or full URLs — so format ambiguity remains.

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+resource ('returns a complete six-part domain profile') and enumerates the six sections, so the agent knows exactly what it aggregates. However, it never distinguishes itself from the very similar siblings netintel_domain_report and netintel_domain_due_diligence, leaving the 'full' qualifier unexplained.

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?

'One premium call' implies the tool consolidates the six individual lookups (dns_lookup, ssl_analyze, whois_lookup, cloud_fingerprint, tech_fingerprint, security_headers), which is implied guidance for when to use it. But there is no explicit when-to-use, when-not-to-use, or any named alternative such as the lighter netintel_domain_report.

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