Create server

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

Annotations already indicate readOnlyHint=false (write) and destructiveHint=false. The description adds the SSH private key prerequisite, which is useful, but it does not disclose other behavioral aspects such as provisioning time, required permissions, or return format. The additional context beyond annotations is limited.

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 just two sentences, efficiently stating the primary purpose and a key requirement. It is concise, front-loaded, and every sentence earns its place.

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 tool with 9 parameters, no output schema, and zero parameter descriptions, this description is too brief. It explains only one prerequisite and omits return value expectations, likely because it is a create operation, and ignores most parameters and potential edge cases. It is minimally viable but has significant gaps.

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 has 9 parameters with 0% description coverage. The description only mentions 'private key UUID', giving minimal meaning for that parameter, but leaves the other eight parameters (ip, name, port, user, proxy_type, description, is_build_server, instant_validate) unexplained. It fails to compensate for the missing schema descriptions, especially for ambiguous fields like is_build_server and instant_validate.

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 new server', specifying the verb and resource. This distinguishes it from sibling tools focused on other resources (createProject, createService, createDatabase) and related server tools like validateServer or updateServer.

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 usage (to create a server) and provides a prerequisite ('Requires a private key UUID for SSH access'), giving some contextual guidance. However, it does not explicitly state when to use this tool versus alternatives, nor does it mention exclusions or comparisons to sibling tools like createService or createPrivateKey.

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