Check Domain Availability

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

With no annotations, the description carries the full burden, but it only restates the tool's name and doesn't disclose behavioral traits like whether it performs a live lookup, rate limits, or that it doesn't actually purchase/reserve the domain. This is a minimal disclosure.

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 one-sentence description is appropriately sized for a simple single-parameter tool and is front-loaded with the essential action. Every word adds value.

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?

The description is sufficient for basic selection but lacks mention of return format or edge cases (e.g., invalid domains). Given no output schema, this leaves the agent to infer the response type.

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 input schema already provides 100% coverage, describing the 'domain' parameter with an example ('example.com'). The description adds no additional parameter semantics, so it stays at the schema-based baseline.

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 the tool checks domain availability for registration, using a specific verb and resource. It distinguishes from sibling domains tools like domains_purchase or domains_get_details.

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 implies the tool's use for checking availability but does not explicitly state when to use it versus alternatives like domains_purchase, nor does it provide exclusions or context such as whether it reserves the domain.

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