subdomains_create

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

With no annotations, the description carries the full burden and does provide some behavioral context: 'confirm: Required' signals a confirmation guard, and impersonate identifies ownership. Still, it does not disclose side effects, failure behavior if the subdomain exists, permission requirements, or whether changes are reversible.

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 compact and front-loaded with the core purpose, followed by a concise parameter list. Every line adds useful information without repetition or filler.

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?

The description covers all parameters and gives a clear example for the subdomain format, and an output schema exists so return values need not be explained. However, it omits important operational context such as whether the parent domain must already exist, what confirm is confirming, and expected behavior if the subdomain already exists.

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 the description fully compensates by explaining all parameters: domain is the parent, subdomain is left-most label only with an example, impersonate is the owning user, and confirm is required. This adds essential meaning the schema lacks.

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 'Create a subdomain' with a specific verb and resource, distinguishing it from subdomains_list and subdomains_delete. It does not explicitly differentiate from domains_create, but the arg list makes the subdomain-specific intent clear.

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 verb 'create' implies use when adding a new subdomain to an existing parent domain. However, the description never explicitly states when to use this tool versus alternatives like domains_create or subdomains_list, and it offers no exclusions or preconditions.

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