shutdown_now

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

With no annotations, the description carries the full burden and discloses key behavioral traits: it forces shutdown, loses unsaved work, and requires an exact confirmation string. It does not mention response behavior or permissions, but for a simple destructive action the essential risks and precondition are covered.

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?

Two sentences, front-loaded with the core action and consequence, with no filler. Every sentence earns its place by conveying action, risk, and a precondition.

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 single-parameter destructive tool without an output schema, the description covers what the tool does, the danger, and the required confirmation. It could more explicitly distinguish the immediate forced action from schedule_shutdown, but the core information needed to invoke it correctly is present.

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 fully documents the confirmation parameter. The description adds context that the string must be exact and that the action is destructive, but it does not add significant new parameter-level meaning beyond the schema's const and description.

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 identifies a specific verb, resource, and timeframe: 'Force Windows to shut down after five seconds.' This clearly distinguishes it from schedule_shutdown, which implies planned rather than immediate forced shutdown.

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—force an immediate shutdown when needed—and highlights the requirement for confirmation, but it does not explicitly state when to prefer this over schedule_shutdown or when not to use it. Usage context is present but not fully articulated.

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