create_server

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

No annotations provided, so the description must cover safety and behavioral traits. It only states the creation action without disclosing any side effects, authorization needs, or rate limits. This is insufficient for a creation tool.

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 concise and front-loaded with the main action. The parameter list is structured and easy to scan. Slight verbosity with 'Args:' label is acceptable.

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 parameter usage with cross-references and notes optionality. Given output schema exists, return value details are not required. It provides enough context for a typical creation task.

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 coverage is 0%, so description fully compensates. Each parameter gets a meaningful explanation (e.g., hostname example, cross-references for location/plan/OS, optional ssh_key_ids with purpose). This adds significant value beyond the schema.

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 VPS server' with a specific verb and resource. It distinguishes well from siblings like list_servers or delete_server, and the parameter list directly supports the action.

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 provides clear context by referencing sibling tools for location, plan, and OS selection, implying prerequisites. However, it does not explicitly state when not to use this tool or provide alternatives for similar actions.

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