Create Site

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

Minimal disclosure beyond the basic action. Only notes that it returns an operation_id, which hints at async behavior. With openWorldHint annotation, more context on side effects or what triggers is needed.

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?

Single, front-loaded sentence that efficiently conveys purpose and key output. No wasted words.

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?

Despite having an output schema and parameter descriptions, the description lacks context on prerequisites (e.g., billing status), region guidance beyond referencing another tool, and any usage caveats. A more comprehensive description would help.

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?

All 11 parameters have descriptions in the schema (100% coverage), so the description adds no additional meaning. Baseline score of 3 is appropriate as the schema carries the burden.

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?

Explicitly states 'Create a new WordPress site on Kinsta', providing a specific verb and resource. Clearly distinguishes from sibling tools like kinsta.sites.clone and kinsta.sites.create-plain.

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?

Implies usage for creating WordPress sites but does not provide explicit when-to-use versus alternatives such as kinsta.sites.create-plain or when not to use. No exclusions or prerequisites mentioned.

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