restart_service

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

With no annotations provided, the description carries full burden. It openly discloses 'STATE-CHANGING operation' and 'REQUIRES human approval before execution', which are critical behavioral traits. It does not mention failure modes or side effects, but given the simple nature of a restart, this is adequate.

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 three sentences with no filler. The core action is front-loaded, the mutating nature and approval requirement are clearly highlighted, and the usage guidance is succinct.

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 (one parameter) and the presence of an output schema, the description covers all essential aspects: purpose, when to use, and critical behavioral disclosure. Minor gaps like error handling or prereq checks are not critical for this simple 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 description coverage is 0%, so the description must compensate. However, it offers no details about the 'service' parameter beyond the tool's purpose—no expected format (e.g., unit name vs. full path), no examples, no constraints. This leaves the agent to infer even basic parameter semantics.

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 states a specific verb ('restarts') and resource ('a systemd service'), and explicitly notes it is the only mutating tool in the set. This distinguishes it clearly from the read-only sibling tools.

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?

It provides clear usage context: 'Use this only when a service needs to be restarted as a remediation step and the user has been informed.' It also explicitly names that it is the only mutating tool, implicitly excluding all read-only alternatives.

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