search_domains

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

No annotations are provided, so description carries full burden. It discloses the 1,000 limit and the output groups (available, taken, noInfo, aftermarket). However, it does not explicitly state that the operation is read-only or any authentication requirements. For a search tool, this is acceptable but not fully transparent.

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?

Two concise sentences front-load the purpose and key constraints. No redundant or unnecessary text; every sentence 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?

For a simple tool with one parameter and no output schema, the description covers purpose, limit, and output categories. It lacks explicit parameter format and behavioral details like idempotency, but overall it is sufficient for an agent to understand basic usage.

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 0% so description must add meaning. The description mentions the 'domains' parameter implicitly by stating 'Bulk domain name search' and the max 1,000 limit, but it does not specify the expected format of domain strings (e.g., 'example.com' vs URL). With only one parameter, more explicit detail would improve clarity.

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?

Description clearly states the verb 'search' and resource 'domains', specifies bulk nature, maximum limit, and output groups (available, taken, etc.). This distinguishes from potential single-domain search tools even though no siblings are listed.

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?

Explicitly mentions maximum 1,000 per call, indicating a bulk use case. No exclusions or alternatives are provided, but given no sibling tools, the guidance is sufficient for the agent to understand when to use this tool.

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