A runbook often relies on the experience of the person reading it. An instruction like “restart the unhealthy service” leaves important questions unstated: which instance, under what conditions, and with what impact?

Write down the assumptions

Define the evidence that makes the procedure appropriate. State the situations in which it should not be used. Name the permissions needed, and make the target unambiguous.

Make success observable

A command completing is not the same as a service recovering. Include a check that reflects the user-visible symptom, a reasonable observation window, and a stop condition if the result is unexpected.

Try it somewhere disposable

Before allowing an agent to follow the procedure, test it in an isolated environment. Ambiguous steps are opportunities to improve the runbook for everyone who depends on it.