instances_perform_server_action

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

No annotations provided. Description adds context that termination is intentionally excluded and points to delete_server for deletion. Does not disclose other side effects like poweroff stopping the server, but actions are self-explanatory.

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 sentence that is concise and front-loaded. No wasted words, but could be more structured with bullet points for actions.

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?

Minimally complete: describes purpose, action options, and a key exclusion. Does not specify prerequisites (e.g., instance must exist) or return details, but output schema exists. Adequate for a simple action 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?

Schema coverage is 100% with detailed descriptions for all parameters. Description adds no extra meaning beyond summarizing the purpose; baseline 3 is appropriate.

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?

Clearly states 'perform a power or lifecycle action on an instance' with specific verb and resource. Distinguished from sibling instance tools like instances_create_server by focusing on actions on existing instances.

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?

Implicitly indicates when to use (existing instance lifecycle actions). Explicitly notes that termination is handled by delete_server, providing an alternative for a specific action. No other when-not guidance.

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