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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety and mutability are covered structurally. The description adds real value beyond that by disclosing the exact payload shape ('inputs, steps, checks, outcome stats and version history'), which is significant because no output schema exists. It stops short of noting failure behavior for an unknown slug or how the per-call token override affects access to private playbooks.

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 zero filler, and the most informative element (the full method card) is front-loaded. It is a bare noun phrase rather than an action statement, which makes it terser than ideal for an agent scanning for a verb to match intent.

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 two-parameter read tool with full annotation coverage and complete schema descriptions, the only burden left to the description is the return surface, and it enumerates the returned sections. Lacking an output schema, it could have been slightly more precise about the structure of those fields, but nothing critical to correct invocation is missing.

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?

Schema coverage is 100%, and the schema itself explains both `slug` and the optional `token` override in detail, including the guest follow-up use case. The description adds nothing about parameters, so the baseline 3 applies — the schema is doing all the parameter work.

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 identifies the resource (a playbook) and signals this is the full-detail read by enumerating the returned content ('inputs, steps, checks, outcome stats and version history'), which implicitly contrasts with the list sibling. It never states the verb explicitly ('read/retrieve by slug'), relying on the title to supply the action, and does not name playbooks_list as the alternative.

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?

There is no when-to-use guidance, no prerequisities (e.g. does the playbook need to exist, are private playbooks hidden), and no mention of the obvious alternative playbooks_list for discovery. Only the word 'full' hints that this is the detail view versus a listing, leaving routing between siblings to inference.

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