restart_panel

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

Discloses that panel and API become briefly unavailable while services remain running, and requires confirmation. Without annotations, the description effectively communicates the tool's impact, though duration and permissions are not specified.

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?

Two concise sentences: first states the action and impact, second specifies the requirement. No unnecessary words, perfectly front-loaded.

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 restart tool with one parameter and no output schema, the description provides purpose, impact, and a clear usage requirement. It adequately covers the expected context without gaps.

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 has 100% coverage and already describes the confirm parameter as mandatory with exact value. The description does not add new meaning beyond the schema, so baseline 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?

Description clearly states the verb 'Reinicia' and resource 'Easypanel', specifying that the panel/API become briefly unavailable but services continue, which distinguishes it from service-level restart tools like restart_service.

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?

Explicitly requires the confirmation string 'CONFIRMO', giving a clear usage prerequisite. Implicitly indicates when to use (restart the panel) but does not explicitly exclude alternative scenarios.

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