Check Domain

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

No annotations exist. While the verb 'check' implies a read-only operation, the description does not explicitly state that no modifications are made, nor does it disclose any caching behavior, error conditions, or output format. This leaves the agent with limited knowledge of the tool's behavior beyond its basic function.

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?

One sentence with no unnecessary words, appropriately brief and to the point.

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?

Although the tool is simple, the description fails to specify what the tool returns (e.g., a boolean, a status string, or an error) and does not mention edge cases like invalid domains or network dependencies. Given the absence of an output schema, this is a meaningful gap.

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 schema has one required string parameter 'domain' with 0% schema coverage, and the description adds no additional details about the expected format (e.g., whether to include the TLD, protocol, or subdomain). The description merely repeats the word 'domain' from the parameter name, providing no extra semantic value.

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's purpose with a specific action ('check') and resource ('domain availability'). It distinguishes from sibling tools like info_domain and register_domain by focusing specifically 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?

No guidance is provided on when to use this tool versus alternatives such as info_domain, get_tld_info, or register_domain. It lacks contextual triggers like 'before registering' or exclusions.

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