check_domains

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

No annotations are provided, so the description carries the burden. It states the tool checks availability and premium pricing, and imposes a max limit of 50 domains—useful constraints. However, it does not disclose behavior for invalid domains, rate limits, or side effects, though the read-only nature is implied.

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 immediately states the purpose and a key constraint. It is front-loaded, concise, and every word earns its place without unnecessary elaboration.

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, single-parameter tool with no output schema, the description covers the core action and a limit. However, it lacks details on expected response format (e.g., whether pricing is returned per domain) which would help an agent complete its task without further inference.

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 covers 100% of parameter documentation with an array of strings and an example. The tool description adds no new semantic detail beyond the schema—'one or more domains' and 'Max 50 per call' repeat schema constraints. Baseline 3 applies as schema already provides sufficient meaning.

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 and premium pricing. It uses a specific verb ('check') and resource ('domains'), and distinguishes itself from sibling tools like 'get_domain_info' or 'get_pricing' by focusing on availability and pricing in a single call.

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 is for checking one or more domains, but does not explicitly state when to use it over alternatives like 'get_domain_info' or 'get_pricing'. No exclusion criteria or alternative tools are mentioned, leaving the agent to infer usage context.

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