reboot_gateway

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It effectively describes the tool's impact ('temporarily disconnect all devices', 'interrupt heating/cooling control'), timing ('1-2 minutes to fully restart'), and caution needed, providing comprehensive behavioral context beyond the basic action.

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 perfectly concise with two sentences that each serve distinct purposes: the first states the action and caution, the second provides timing information. There's no wasted language or redundancy.

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 zero-parameter destructive operation with no annotations or output schema, the description provides excellent context about impacts and timing. It could slightly improve by mentioning whether user confirmation is needed or what happens after reboot completes, but it's largely complete for this tool type.

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 tool has 0 parameters with 100% schema description coverage, so no parameter documentation is needed. The description appropriately focuses on behavioral aspects rather than repeating parameter information that doesn't exist.

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 specific action ('reboot') and target resource ('Plugwise gateway'), distinguishing it from sibling tools like 'set_gateway_mode' or 'control_switch'. It precisely communicates the tool's function without ambiguity.

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 provides clear contextual guidance ('Use with caution as this will temporarily disconnect all devices and interrupt heating/cooling control'), indicating when this tool should be used carefully. However, it doesn't explicitly mention when to choose alternatives like 'set_gateway_mode' for non-reboot adjustments.

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