add_domain

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

With no annotations, the description carries the full behavioral burden and it discharges only one part: it discloses that the operation is gated on DNS checks. It says nothing about what happens when checks fail, whether the domain is created but unverified, whether verification is asynchronous, what permissions are required, or what the response contains. The single DNS-gating disclosure is genuinely useful context beyond structured data, but for an unannotated mutation tool the coverage is thin.

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 short but wastes roughly half its length restating the same sentence twice, with a malformed double period between the copies. Nothing is front-loaded incorrectly, but duplication is a clear structural defect rather than concision.

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?

This is a low-complexity tool (one parameter), which lowers the bar, but with no annotations, no output schema, and no parameter documentation, the description is the only source of behavioral information and it supplies just one fact (DNS checks). An agent still cannot tell what a failure looks like, whether the domain enters a pending state, or what prerequisite records must exist, which is meaningful missing context for a mutation tool.

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% for the single required parameter, so the description could have added value by specifying format (apex domain vs. subdomain, whether to include a trailing dot, scheme, or path). It does not, though the parameter's meaning ('domainName') is essentially self-evident from the tool's stated purpose, leaving this at minimum viable rather than broken.

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 verb and resource ('Adds a domain'), so an agent can immediately tell this is a creation operation, distinct in intent from siblings like list_domains, delete_domain, or update_domain_settings. It does not explicitly name or differentiate itself from those siblings, and the sentence is duplicated with a stray double period, but the core purpose is unambiguous.

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?

There is no when-to-use guidance, no statement of preconditions the caller must arrange (e.g., whether an ownership code must be obtained first, as the get_ownership_code sibling suggests), and no mention of alternatives such as update_domain_settings for existing domains. The only hint is that the add is conditional on passing DNS checks, which is a precondition rather than routing guidance.

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