postpone_shutdown

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It explains the sign semantics of the minutes parameter, but it does not disclose what happens when no shutdown is active, whether the previous schedule is replaced, whether the operation requires elevated privileges, or any error behavior.

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, focused sentence that is front-loaded with the action and resource, then clarifies the parameter semantics. Every word earns its place and there is no filler.

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 simple one-parameter tool, the description covers the main action and parameter meaning. However, with no annotations and no output schema, it leaves gaps around prerequisites (an active shutdown), failure behavior, and how this relates to the sibling scheduling tools.

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 schema only describes 'minutes' as an integer with bounds, providing 0% semantic coverage. The description adds the key meaning that a positive value moves the shutdown later and a negative value moves it earlier, which is essential for correctly interpreting the sign of the 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 action ('Move') and a specific resource ('active Windows shutdown'), and explains the core behavior of shifting by a signed number of minutes. It does not explicitly name a sibling, but the phrase 'active Windows shutdown' distinguishes this from schedule_shutdown, cancel_shutdown, and shutdown_now.

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 this tool is for adjusting an already-scheduled shutdown, as opposed to creating or canceling one, but it never states when to choose this tool over schedule_shutdown or shutdown_now. No exclusions or prerequisites are mentioned, leaving the agent to infer the appropriate context.

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