create_domain

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

With no annotations, the description carries the full disclosure burden. It usefully reveals that the tool never modifies DNS itself, a significant behavioral trait beyond the simple 'create' verb, and it discloses the return contents: DNS records and a setup recommendation. This is strong transparency for a single-parameter 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?

Two sentences are economical and front-loaded: the core purpose appears immediately, and the crucial caveat (no DNS modification) is placed clearly. No word is wasted.

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 tool with one simple parameter and no output schema, the description adequately explains what happens and what the agent receives. It also covers the key behavioral boundary and the necessary follow-up action, making it fully complete.

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 documents the only parameter, domain, with a clear format example. With 100% schema coverage, the description does not need to add much; it simply references the domain but does not go beyond the schema's 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 states a specific action—register a domain—and specifies the resource ('a domain') and the outcome (returns exact DNS records and setup recommendation). It clearly distinguishes itself from sibling tools like verify_domain or delete_domain by naming its unique role and boundary.

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 gives clear context: use this tool to register a domain and obtain DNS records, then add those records yourself. It also tells the agent what it must do afterward, though it does not explicitly name alternatives or say when not to use the tool.

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