create_system_restart

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

The endpoint implies a restart, but the description never states what happens: it does not mention that the system will reboot, that active operations may be interrupted, or what the response/result means. Annotations give idempotentHint=true and readOnlyHint=false, but the description itself adds almost no behavioral detail.

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 extremely short, but the opening line 'Create System.' is wasteful and actively confusing; it does not convey the restart behavior. The endpoint is the only informative part, so the structure is concise but not effective.

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?

Even though this is a zero-parameter call with an output schema, the description omits the essential context of what calling the endpoint does and when it should be used. For a system-restart operation, it should at minimum say that it restarts the system and warn about impact.

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 100% schema coverage, so there is no parameter meaning for the description to add. The baseline of 4 applies because no parameter documentation is needed.

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 says 'Create System,' which is misleading—it does not say the tool restarts anything. The only useful clue is the endpoint 'POST /api/v1/system/restart', from which the action can be inferred, but the description itself fails to state the operation clearly or 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?

There is no guidance on when to use this tool vs. alternatives such as create_system_shutdown or create_system_backup_restore_by_id. No context, trigger conditions, or exclusions are provided.

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