Start/stop/restart service

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

Annotations already declare readOnlyHint=false and destructiveHint=true, establishing that this is a mutating and potentially destructive operation. The description adds no extra context about side effects, such as downtime, the order of stop/restart, or whether changes are reversible, which would be valuable for a destructive tool.

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 filler. Every word contributes to conveying the tool's purpose.

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 simple with two required parameters and clear annotations, but the description omits details about the outcome (e.g., whether it returns an updated service object, if it's synchronous) and potential side effects. Given the destructive hint, a bit more context would round it out, but it is otherwise adequate for a control operation.

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?

With 0% schema description coverage, the description must compensate. It does clarify that 'uuid' identifies a service and 'action' takes values start/stop/restart, adding semantic meaning beyond raw schema types. However, it does not elaborate on any constraints or the meaning of each action beyond the enum.

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 'Start, stop, or restart a service by UUID' clearly states the specific verbs and the resource type, distinguishing it from sibling tools that operate on applications or databases. It is unlikely to be confused with other lifecycle operations.

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?

Usage is implied: use this tool when you need to control a service. However, there is no explicit guidance on when to prefer this over sibling tools like startApplication/stopApplication or controlDatabase, nor any mention of prerequisites.

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