Reboot an endpoint

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

Annotations already indicate destructiveHint=true, and the description merely states 'Reboots the host' without adding behavioral context such as expected side effects, prerequisite permissions, or what happens during the reboot. The mention of 'reboot action template' is minimal extra information.

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 two sentences with no fluff. The first sentence clearly states the action, and the second provides a useful tip for combining with another tool, making it efficient and front-loaded.

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 8 parameters, output schema, and annotations, the description covers the core action succinctly. It misses some behavioral nuance (e.g., confirmation requirement, dry-run default) but remains adequate for a reboot tool with good schema coverage.

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 baseline is 3. The description does not add any parameter-specific meaning beyond what the schema already provides, so no extra value is added.

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 'Reboots the host via the reboot action template', specifying the verb and resource. The title 'Reboot an endpoint' reinforces the purpose, and the action is distinct from sibling tools like create or delete operations.

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 hints at combining with action1_wait_for_automation for recovery tracking but does not explicitly state when to use or avoid this tool, nor does it clarify prerequisites or alternatives among the many sibling tools.

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