manage_service

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

With no annotations provided, the description carries the full burden of behavioral disclosure, but it does not mention side effects (e.g., start/stop alter service state), permission requirements, or output behavior. The listed actions imply mutation for some, but the description does not elaborate on what the agent should expect from status or logs compared to start/stop.

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 a single sentence that front-loads the core purpose and lists actions parenthetically. It is concise with no wasted words, earning a perfect score for conciseness and structure.

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?

The tool has multiple actions and no output schema, so the description should explain more about expected results and side effects, but it does not. It omits the reload and logs actions and fails to describe the behavior of each action or the response format, which is a significant gap for an agent.

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 input schema already describes all parameters with 100% coverage, so the baseline is 3. The description does not add additional meaning about parameter usage; it only lists a subset of the actions, omitting reload and logs, and does not explain the log_lines parameter's role.

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 identifies the tool's function: managing systemd services on a VPS, with an explicit list of common actions like start, stop, restart, status, enable, and disable. This distinguishes it from sibling tools such as run_command (generic command execution) and list_services (listing only). The verb 'manage' plus the resource and action examples provides a specific and unambiguous purpose.

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 implies usage for systemd service operations on the VPS, but it does not explicitly state when to use this tool over alternatives or when not to use it. There are no exclusion criteria or references to sibling tools like docker or run_command, leaving the agent to infer the appropriate context.

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