server_service

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

With no annotations, the description usefully discloses that status is read-only and immediate while mutation actions show a preview first. It does not explain how the preview is confirmed/executed, what permissions or root behavior apply, or which actions can disrupt the service.

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 short sentences, front-loads the core purpose and actions, and includes only behaviorally relevant details. There is no wasted wording.

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?

An output schema exists, so return values need not be described. The preview workflow is a helpful addition, but for a five-parameter mutation-capable tool with no annotations and 0% schema coverage, more parameter and permission context is needed.

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 0% for five parameters, so the description must compensate. It clarifies the action values and the status-vs-preview behavior, but leaves host, unit, as_root, and confirm undocumented.

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 and resource: managing a systemd service, and enumerates the supported actions. It is clearly distinct from Docker and file-management siblings, but it does not explicitly differentiate itself from adjacent server tools such as server_processes or server_power.

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 action list and the note that status runs immediately while other actions preview first imply the intended workflow. However, there is no explicit guidance on when to prefer this tool over alternatives or when not to use it.

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