Добавление поддомена

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

The description simply states the creation action, which aligns with the non-read-only annotation. It does not add additional behavioral context beyond what annotations already provide, such as potential DNS propagation or idempotency effects.

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 brief and front-loaded, stating the action and required inputs in two sentences with no superfluous content.

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 two-parameter creation tool with annotations covering the safety profile, the description is largely sufficient. However, it omits explicit prerequisites (e.g., main domain must exist) which would make 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 schema already fully documents both parameters with descriptions. The description restates that FQDN of main domain and subdomain are required, adding no new semantic 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 clearly states it creates a subdomain for a specified main domain, using a specific verb and resource. It distinguishes from sibling tools like add_domain by targeting subdomains specifically.

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 the tool is used when adding a subdomain to an existing domain, but does not explicitly state when to use it over alternatives or provide exclusions. No guidance is given for scenarios like domain verification or existing subdomains.

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