opspilot_restart_service

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

With no annotations, the description carries the transparency burden. It discloses an important behavioral trait: this is a request for local approval, not a direct restart, and it targets a single registered service. However, it does not explain what happens after approval, whether it blocks, potential side effects, or required permissions.

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, front-loaded sentence with no wasted words. Every phrase adds value: 'Request' states the action, 'single registered service' scopes the resource, and 'for local approval' clarifies the workflow.

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 no output schema, no annotations, and an input schema with no parameter descriptions, so the description must compensate. It fails to cover host_alias semantics, approval workflow behavior, return values, or prerequisites, leaving significant contextual gaps.

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 has 0% description coverage, and the tool description adds no meaningful parameter details. 'host_alias' is never mentioned, and 'service' is only vaguely tied to 'registered service' without clarifying accepted values, formats, or relationships.

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 uses a specific verb ('Request') and resource ('service restart') with clear scope ('single registered service') and process context ('for local approval'). This clearly distinguishes it from sibling tools like opspilot_status or opspilot_get_request, which serve different purposes.

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 when to use the tool—when you need to request a restart of a single registered service for local approval—but it does not explicitly state alternatives or when not to use it. There is no mention of using opspilot_status for checking status or opspilot_get_request for viewing existing requests.

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