Перезагрузить роутер

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

Annotations already mark the tool as destructive and non-read-only. The description adds important context beyond the annotations: the server-config prerequisite, that the RCI request format has not been validated against a live device in this project, and that dryRun plus user confirmation should precede real use.

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 short sentences, each carrying distinct information: the action, the configuration prerequisite, and the safety caveat. Nothing is redundant with the title or the schema, and the most important behavioral risk is disclosed early.

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 two-parameter tool with no output schema, the description covers the prerequisite, the safety workflow, and the uncertainty about the RCI payload. It does not detail the exact response for a real reboot, but that is a minor gap given the schema already explains the dryRun return value.

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 schema already documents both boolean parameters in full, including dryRun returning an RCI payload and confirm being required for a real change. Since schema coverage is 100%, the description adds little strictly parameter-level information beyond recommending an invocation order, so the baseline score of 3 is appropriate.

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 opens with a clear, specific statement: 'Немедленная перезагрузка роутера.' It identifies both the action (reboot) and the resource (router), and this operation is distinct from all sibling tools, which are mostly read-only queries or configuration setters.

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 usage conditions: it requires ALLOW_DESTRUCTIVE=true, recommends running dryRun first, and requires explicit user confirmation before the first real use. It does not explicitly say when not to use it, but the safety guidance effectively tells the agent how to gate invocation.

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