reboot_container

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

The description merely states 'Reboot a container,' which implies a restart but offers no details on force vs graceful shutdown, impact on running processes, or return behavior. With no annotations provided, the description carries the full burden of disclosure and falls short.

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 very concise (one sentence plus parameter list), which is efficient, but it omits important information. It is not overly verbose but sacrifices completeness for brevity.

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 existence of an output schema and sibling tools, the description lacks details on return values, side effects, and how reboot differs from similar operations like shutdown+start. It is insufficient for an agent to use the tool correctly without additional inference.

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 description explains each parameter briefly ('node: The node name.' etc.), adding some meaning beyond the schema (which has only names and types). However, it doesn't elaborate on the timeout default or behavior, and schema coverage is 0%, so the description partially compensates but not fully.

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 'Reboot a container,' which is a specific verb and resource. It distinguishes itself from sibling tools like start_container or stop_container by using a different action. However, it does not elaborate on the exact meaning of reboot (e.g., that it involves a stop and start sequence).

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 like shutdown_container followed by start_container, or when to use timeout. There is no mention of prerequisites or exclusions.

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