Restart Ploi server

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

Annotations already indicate destructive behavior. Description adds no extra context about consequences (e.g., downtime, queued jobs), authentication needs, or whether restart is graceful. Fails to augment annotation data.

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?

Extremely concise and front-loaded. However, it is so minimal that it borders on under-specification; a slightly more descriptive verb (e.g., 'rebbot' is fine but could be 'gracefully restart') would improve clarity without losing conciseness.

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 low complexity (single param, no output schema), the description is minimally complete. However, it omits any mention of return value or side effects beyond the destructive hint, which an agent might need for a reboot operation.

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% for the single parameter. The description ('Reboot a Ploi server') adds no additional meaning beyond the schema's 'Ploi server ID.' Baseline score of 3 applies.

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 specifies the action ('Reboot') and the resource ('a Ploi server'). It differentiates from sibling tools such as ploi_update_server and ploi_restart_container.

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?

No guidance on when to use this tool versus alternatives like ploi_update_server or when not to use it (e.g., server must be running). No preconditions or context provided.

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