Lock, reboot, or shut down

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

With no annotations provided, the description carries the full burden. It explicitly discloses the destructive consequence of reboot/shutdown by stating they 'terminate the desktop session' and the permission requirement. This is honest and sufficient for a power action, though it doesn't describe other side effects like unsaved work loss.

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?

A single, information-dense sentence that front-loads the availability of 'lock' and then states the critical constraint. No filler, every clause earns its place.

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 primary caveat (dangerous actions require permission). It doesn't describe return values, but that is acceptable for a mutation tool with no output schema. The agent has enough information to invoke it correctly.

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 0%, so the description must compensate. It adds meaning to the enum values by explaining that lock is safe and always available, while reboot and shutdown are dangerous and gated. This provides the key semantic distinction beyond the raw enum names.

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 title explicitly states 'Lock, reboot, or shut down' and the description names all three actions. It also distinguishes their availability ('Lock is always available') and the prerequisite for reboot/shutdown, making the tool's purpose unmistakable and distinct from any sibling tool.

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 gives clear usage context: lock can always be used, while reboot/shutdown require enableDangerous because they end the desktop session. This implicitly tells the agent when it is appropriate to use each action, though no alternatives are mentioned (there are none among siblings).

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