power_action

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

With no annotations, the description discloses the double-gating to prevent accidental data loss and the required permission. It doesn't detail the exact effects of reboot vs poweroff or error conditions.

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 concise with two sentences, front-loading the purpose and key behavioral information. It avoids unnecessary words but could be more structured.

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?

The description is brief but covers the essential purpose and a key safety behavior. It lacks explanation of output/return values, though an output schema exists. Adequate for a simple tool but incomplete.

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 0%, and the description only hints at possible actions ('reboot / poweroff') without explicitly mapping them to the 'action' parameter. The parameter's allowed values are unclear.

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 is for reboot or poweroff actions, distinguishing it from sibling tools like suspend_system. However, it doesn't explicitly specify the allowed action parameter values.

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 implies usage for power actions and mentions the need for SYSCONTROL_ALLOW_POWER permission, but doesn't provide explicit when-to-use or when-not-to-use guidance compared to alternatives.

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