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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds that it returns the playbook 'in full' and enumerates content elements, which provides some context beyond the bare annotations. However, it does not disclose authentication, rate limits, or error behavior, and the output schema likely already describes the return structure, so the added value is moderate.

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, tightly worded sentence that front-loads the core action ('Read one playbook in full') and then enumerates the included elements without redundancy. Every word earns its place, and no fluff or repetition exists.

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 simple read-only tool with one parameter, rich annotations, and an output schema, the description is nearly complete: it states the operation, the resource, and the key contents. It does not mention how to discover a slug (e.g., via list_playbooks) or handle not-found cases, but these are minor gaps given the schema and annotations.

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?

The input schema has 100% coverage: the slug parameter is fully documented with type, requirement, and an example. The description does not add any additional meaning to the parameter, so the baseline of 3 applies as the schema carries the semantic weight.

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 uses a specific verb ('Read') and resource ('one playbook'), and explicitly states the scope ('in full') and the contents (every step with owner, tool, pitfalls, definition of done, KPIs). This clearly distinguishes it from sibling tools like list_playbooks (which lists) and other get_* tools for different resources.

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?

The description implies usage when you need complete details of a single playbook, but it does not explicitly mention alternatives or when not to use it. There is no reference to list_playbooks for finding slugs or to other get_* tools for different resource types, so the guidance is implied rather than explicit.

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