restart_service

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

Describes default reload behavior, implications of force_restart (service interruption, process termination), permissions, timeout, blocked MCP service, and error conditions. No annotations provided, so description fully covers behavioral traits.

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?

Single paragraph covering all aspects, but slightly dense. Could benefit from slight structuring, but every sentence adds value.

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?

Covers purpose, parameters, behavior, prerequisites, alternatives, response format, and error conditions. No missing elements given the tool's complexity and absence of output schema.

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 0% description coverage; description explains name must be in whitelist and force_restart controls reload vs restart, adding critical meaning beyond schema.

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 clearly states the tool reloads or restarts a systemd service, with specific verbs and resource. It distinguishes from sibling tools reload_service and service_status.

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 states when to use (reload vs restart via force_restart), when not to use (prefer reload_service or service_status), and prerequisite (name must be in whitelist, consult get_service_whitelist).

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