netintel_domain_availability

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

With no annotations provided, the description carries the full burden, and it does disclose useful behavior: the lookup method (RDAP and DNS) and the returned fields (availability status, registrar, expiry per TLD). It is silent, however, on rate limits, partial-failure behavior across the 10 TLDs, and whether results are live or cached.

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?

Two tight sentences with the capability front-loaded and the return payload second; nothing is wasted. It is efficient, though it spends no words on the input ambiguity that most needs resolving.

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 and no output schema, the description does useful work by enumerating the return fields. The remaining hole is the input contract and error/partial-result behavior for a multi-TLD sweep, which an agent cannot infer from the schema.

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% for the single 'domain' parameter, so the description must compensate and does not. It never clarifies the expected input format — a registrable name only versus a full domain with TLD — which is the single most consequential ambiguity given the tool iterates over 10 TLDs itself.

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?

Names a specific verb+resource ('Check if a domain is available for registration') and adds distinguishing scope ('across 10 TLDs simultaneously using RDAP and DNS'). An agent can tell this apart from netintel_domain_vet, netintel_whois_lookup, and netintel_domain_age by outcome, though no sibling is named explicitly.

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?

There is no when-to-use guidance, no statement of prerequisites, and no routing to alternatives such as netintel_domain_vet (reputation) or netintel_tld_price (pricing) for related questions. Usage is only implied by the verb 'check ... for registration'.

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