Setup VPS

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

With no annotations, the description carries full responsibility for behavioral disclosure. It only says 'Setup' without explaining side effects, whether it is destructive, required permissions, or what happens to existing data on the VM. For a provisioning operation, this is a significant gap.

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 a single, well-front-loaded sentence with no unnecessary words. It efficiently communicates the core action and target.

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 tool has 6 parameters, no output schema, and no annotations. The description fails to mention prerequisites (e.g., VM must be purchased), postconditions, or return values, leaving a complex setup operation underspecified. It needs more detail to be fully useful.

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 provides 100% coverage for all 6 parameters with descriptions, so the baseline is 3. The description adds a slight conceptual mapping by linking 'OS' to template_id and 'credentials' to password/public_key_ids, but it does not go beyond what the schema already states.

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 states a specific action ('Setup') on a clear resource ('purchased virtual machine') with scope ('OS and credentials'). It distinguishes from vps_purchase (buying) and vps_recreate (recreating), though not explicitly naming alternatives. The verb 'setup' is slightly generic but the context makes it clear enough.

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 this tool is used after a VM is purchased ('purchased virtual machine'), but it does not explicitly state when to use it, when not to use it, or mention alternative tools like vps_purchase or vps_recreate. The usage context is implied but not spelled out.

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