ctrl_alt_delete

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

Annotations already flag destructive=true, but the description adds that this is a keyboard-delivered reboot, classifies it as power_soft, and requires the KVM_PILOT_MCP_ALLOW_POWER permission. This goes beyond the annotation by specifying the permission model and the nature of the operation (power control vs. HID input).

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?

Three compact sentences that front-load the action, then explain the destructive nature and permission requirement. No wasted words; all information is relevant.

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 destructive power tool, the description covers the core behavior and permissions, but lacks essential parameter semantics. Given the absence of an output schema and the simplicity of the tool, the major gap is the unexplained parameters, preventing full autonomous use.

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% and the description provides no explanation of the 'confirm' or 'profile' parameters. Since both are optional but could affect behavior (e.g., confirmation for destructive action), the agent has insufficient information to use them correctly.

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?

Clearly states 'Send Ctrl+Alt+Del to the managed host' — a specific verb and resource. It further clarifies this triggers a reboot and distinguishes it from regular HID shortcuts by referencing the power gate and classification as power_soft, differentiating it from sibling tools like send_shortcut.

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?

Provides clear context that this is a power-related operation requiring the same permission gate as the 'power' tool, and warns against using the weaker HID gate. However, it doesn't explicitly name alternative tools or state when not to use it, though it implies that regular HID shortcuts are not equivalent.

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