iaas_reboot_machine

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

Annotations already declare that this is not read-only, is open-world, is not idempotent, and is not destructive. The description adds essentially no operational context beyond the endpoint, such as disruption caused, preconditions, or expected effect on running workloads.

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 short, but it repeats the same 'reboot operation for machine' concept twice without adding information. The unexplained 'Second day reboot operation' sentence is confusing rather than useful.

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 state-changing reboot operation surrounded by many power-state siblings, the definition lacks the distinction and operational context an agent needs to choose it correctly. Annotations and schema cover safety and parameters, but the description does not complete the selection picture.

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%, so the schema already documents both parameters. The endpoint path reinforces that id is the machine identifier, but the description does not add further meaning for apiVersion or the id parameter.

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 verb and resource: reboot a machine, and includes the concrete operation endpoint. However, it does not distinguish this from siblings like iaas_restart_machine, iaas_reset_machine, or iaas_power_off_machine.

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?

There is no guidance on when to use reboot versus restart, reset, power off, or shutdown. It also omits prerequisites such as whether the machine must be powered on. The phrase 'Second day reboot operation' is too unclear to function as usage guidance.

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