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

Mentions the method of checking (DNS and RDAP), which provides some behavioral context. However, no annotations exist, and the description does not disclose potential costs, rate limits, or whether the operation is truly read-only beyond what is implied. Bare minimum transparency for a simple check tool.

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?

Single sentence, 15 words, no wasted words. Efficient and direct, but could be slightly improved by front-loading the core purpose more prominently (though it already does).

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?

Adequate for a simple tool with one parameter and no output schema, but fails to describe the return format or error conditions. The agent does not know if the response is boolean, string, or structured, which is a gap given the complexity level.

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 a clear description of the single parameter 'domain'. The tool description adds no additional meaning beyond what is in the schema. Baseline 3 due to 100% schema coverage.

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?

Clearly states the verb 'checks' and resource 'domain availability', distinguishing from sibling tool 'check_tlds_tool' by specifying it checks domains for registration availability. The description is specific and actionable.

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 on when to use this tool versus the sibling 'check_tlds_tool'. Lacks any contextual instructions about prerequisites, domain format restrictions, or when to prefer alternative tools.

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

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

With no annotations provided, the description carries the full burden of behavioral transparency. It states the tool checks 'across multiple TLDs' but gives no details on which TLDs, how availability is determined, or any side effects (e.g., rate limits, caching). This minimal disclosure is insufficient for an agent to understand the tool's full behavior.

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 a single sentence that is front-loaded with the core action ('Checks a keyword across multiple TLDs') and includes the outcome ('find available domain names'). Every word is necessary and there is no redundancy or filler.

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?

Given the simplicity of this tool (one parameter, no output schema) and the presence of a sibling, the description should explain what 'available' means, whether there are limitations on TLDs checked, and how results are returned. The current description leaves significant gaps, making it incomplete for an agent to use effectively without additional context.

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 100%, so the baseline is 3. The parameter 'keyword' already has a clear description in the schema ('String representing the keyword to check across TLDs (e.g., "myapp")'). The tool description adds no new semantic information beyond what is in the schema, thus it does not improve the 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 a keyword across multiple TLDs to find available domains, using a specific verb and resource. However, it does not explicitly differentiate from the sibling tool 'domain-checker_check_domain_tool', which likely checks a specific domain rather than a keyword across TLDs. A brief contrast would elevate it to 5.

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 the sibling 'domain-checker_check_domain_tool'. The context signals list the sibling but the description lacks any mention of scenarios where one should prefer this tool over the other, leaving the agent without decision criteria.

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