hosting_createWebsiteV1

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

Discloses that website creation is asynchronous ('takes up to a few minutes') and suggests a polling mechanism. Explains that first website sets up a hosting account and subsequent ones reuse the datacenter. No annotations provided, so description carries full burden and does so adequately.

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?

Six sentences, each adding value. Front-loaded with main purpose. Clear structure. Could be slightly more structured, but no unnecessary information.

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?

Given no output schema and no annotations, the description covers key aspects: required parameters, datacenter behavior, async nature, and how to verify completion. It does not cover error cases, but is sufficient for a creation 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?

Input schema covers all 3 parameters with descriptions. The description adds valuable context for datacenter_code, explaining its role in setting up new hosting accounts and automatic reuse. For domain, schema already includes restriction ('Cannot start with www.'). Overall, description complements schema well.

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?

Description clearly identifies the action ('Create') and resource ('new website'). It distinguishes from sibling tools like hosting_deployJsApplication by focusing on creating a website from an order, not deploying a specific application.

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?

Provides clear instructions on when to use the datacenter_code parameter (first website on a new plan) and explains subsequent behavior. Also advises polling the list endpoint for completion, handling the async nature. Does not explicitly exclude alternatives, but context implies usage.

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