Reboot a node

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

Discloses key behaviors beyond annotations: node unreachable for 30-60s, session ends, and equivalence to admin command. Combines with annotations (destructiveHint=true) to give a full picture.

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?

Very concise: two sentences plus a warning symbol. Front-loaded with the core action and target. No unnecessary words.

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?

Given the presence of an output schema and the tool's low complexity (2 optional params), the description fully covers usage, behavior, and effects. No gaps identified.

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% and description does not add new information beyond schema for parameters. The description repeats the schema's note on omitting node but does not elaborate on dryRun.

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 action ('Reboot a node'), specifies the target types (home companion or remote repeater), and distinguishes behavior when node parameter is omitted. It effectively differentiates from sibling tools by being the top-level reboot command.

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 guidance on when to omit the node parameter and notes equivalence to an admin command. However, does not explicitly discuss when not to use the tool or compare with sibling alternatives like 'admin'.

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