openstack_server_action

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It fails to mention side effects, whether actions are synchronous/asynchronous, permission requirements, or idempotency. The description merely restates the action names without explaining consequences or edge cases.

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, concise sentence that front-loads the primary verb and resource. It is efficiently worded with no filler, making it easy to scan. All content is relevant, even if brief.

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?

Given the tool's mutation nature, lack of output schema, and absent annotations, the description is incomplete. It does not explain return values, error conditions, or state-transition rules (e.g., cannot pause a stopped server). The enum provides options but not the context needed for safe usage.

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 description coverage is 100%, so all parameters (action, device_id, server_id) are already described in the schema. The description adds minimal value by listing some action values that are already in the enum. No additional semantic detail about device_id vs server_id is provided 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 the tool's purpose: 'Perform an action on an OpenStack server' and lists several concrete actions (start, stop, reboot, pause, suspend, resume). This distinguishes it from sibling tools like openstack_list_servers and openstack_server_detail. However, it omits some enum actions (hard-reboot, unpause) and could be more explicit about state management.

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?

No guidance is provided on when to use this tool versus alternatives, nor are there any prerequisites or conditions for choosing specific actions. The description does not clarify that start is for stopped servers, stop is for running servers, etc. Usage is only implied by the tool's existence.

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