playbook

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety is covered structurally. The description adds that the payload contains session procedure and safety rules, which sets expectations about content, but says nothing about length, format, or whether the whole document must be consumed.

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?

A single compact sentence with the directive front-loaded ahead of the content summary. Nothing is wasted, though the phrasing is slightly compressed to the point of reading as a label rather than prose.

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?

For a zero-required-parameter, read-only guidance tool with no output schema, the description conveys enough: what it contains and that it should be read first. Only the shape of the returned material is left unstated, which is a minor gap for a documentation tool.

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?

There is a single optional parameter whose schema description already fully documents the adb serial and the multi-phone condition it addresses. The description does not reference the device argument at all, so it adds no meaning beyond the 100%-covered schema; baseline 3 applies.

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 specifies the content of the resource: operational instructions for running a session with the device owner plus safety rules. That distinguishes it from the sibling action tools (apply_plan, tweak, undo), though it never explicitly says it returns a document rather than performing an operation.

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?

'Read this first' is an explicit ordering directive that tells the agent to consult this before invoking any of the sibling tools. It establishes both the trigger (start of session) and priority relative to alternatives.

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