dynadot_search

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

With no annotations, the description is relied upon for transparency. It discloses auto-punycode for IDNs and the domain limit, but does not describe the response format, side effects, or whether pricing is returned when requested.

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 extremely concise with two sentences, front-loading the key action. Every sentence adds value without redundancy.

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 search tool with complete parameter descriptions, the description is adequate but lacks mention of return values or behavior when domains are unavailable. Without an output schema, returning results would benefit from clarification.

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 coverage is 100%, so baseline is 3. The description adds context for the 'domains' parameter (limit of 100) but provides no extra detail for 'showPrice' or 'currency' beyond schema descriptions.

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, specifying the resource (domains) and action (check). It mentions the limit of 100 domains, but does not explicitly differentiate from sibling tools like dynadot_bulk_search.

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 usage for checking domain availability and provides a limit, but offers no guidance on when to use this tool over alternatives like dynadot_bulk_search or dynadot_domain_info.

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