Restart service

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

Annotations indicate readOnlyHint=false and destructiveHint=false, and openWorldHint=true. The description adds that it restarts all containers and can pull images if `latest` is set, which are useful behavioral details. However, it doesn't mention potential downtime or side effects on connections, which could be relevant but isn't a contradiction.

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 two concise sentences, front-loaded with the core purpose and a concrete example. It avoids unnecessary detail and is easy to scan.

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 is a simple restart operation with full schema coverage and no output schema. The description provides the key usage context and the flag explanation. It could explicitly distinguish from restart_application, but the tool name and description make it reasonably clear.

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?

Both parameters are fully documented in the schema (100% coverage), including the meaning of `latest` and the flexible format for `service`. The description essentially repeats the schema's explanation for `latest` and adds nothing new about parameters, so it adds minimal value beyond the 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 action ('Restart') and the resource ('a service (all its containers)'), and provides a concrete use case ('after changing its env vars'). This distinguishes it from sibling tools like restart_application, which targets applications rather than services.

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 gives a specific context for when to use the tool (after changing env vars) and explains the `latest` flag. However, it doesn't explicitly mention alternatives or when not to use it, such as comparing to restart_application. Still, the use case provides clear guidance.

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