create_system_restart

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

Annotations already indicate this is non-read-only, idempotent, and non-destructive, but the description adds no behavioral context beyond repeating the endpoint. It never warns that restarting the system will temporarily interrupt service or that privileged access may be required. No contradiction with the annotations exists.

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 short but not effectively concise: 'Create System.' is filler that obscures the restart action, and the useful endpoint is separated from that misleading label. This is under-specification rather than disciplined 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?

For a zero-parameter tool with an output schema and annotations, the description does not need to document parameters or returns. However, it omits the operational consequence of restarting the system and the misleading 'Create System.' wording makes it less complete than a simple 'Restarts the system' would be.

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 zero parameters and the input schema fully covers that, so the description owes no parameter-level detail. The endpoint implies a parameterless call, and there is nothing more the description needs to explain here.

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 first sentence 'Create System.' is vague and misleading—it does not name 'restart' and merely restates part of the operation name. The embedded POST /api/v3/system/restart URL reveals the intended action, but the prose itself fails to clearly state that this tool restarts the system or to distinguish it from create_system_shutdown.

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 no guidance on when to use this tool versus alternatives. It contains only a generic label and an HTTP endpoint, with no preconditions, no effect context, and no mention of related operations like create_system_shutdown.

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