domains_checkDomainAvailabilityV1

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

With no annotations, the description discloses the rate limit and TLD format requirements. However, it does not describe the response structure or behavior on different outcomes (e.g., unavailable domain, errors), leaving some ambiguity.

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 concise (7 lines) and well-structured with clear sections. Each sentence adds value, no redundancy, and the most critical info appears first.

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 check tool with 3 parameters and no output schema, the description provides sufficient context: purpose, usage hints, rate limit, parameter format, and recommendation. An agent can confidently invoke it.

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 describes all 3 parameters (domain, tlds, with_alternatives). The description adds context: multiple TLDs allowed, using with_alternatives with one TLD, and TLD format (no leading dot), enhancing usability beyond the schema.

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 states 'Check availability of domain names across multiple TLDs', using a specific verb and resource. It distinguishes from sibling tools like domains_getDomainDetailsV1 and domains_purchaseNewDomainV1 by focusing on availability checks.

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 explicitly recommends using this endpoint 'before purchase', explains how to check multiple TLDs and get alternatives, and notes the rate limit. It does not explicitly exclude alternatives, but context is clear.

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