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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so safety is covered. The description adds genuinely new behavioral information: the return is the complete Markdown body rather than a summary or metadata, and it characterizes what that body may contain. It does not mention behavior for a nonexistent name, which is the remaining gap.

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?

One sentence, front-loaded with the return value, with no filler. The colon-separated taxonomy of playbook kinds is dense but earns its place by telling the agent what it is about to read.

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?

With no output schema, the description carries the burden of describing the return, and it does so by specifying full Markdown and the three possible content types. For a one-parameter read tool with strong annotations, the only missing piece is failure behavior on a bad name.

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 single parameter already documents that it must come from list_playbooks. The description restates that constraint and hints at the variety of valid names but adds no format, casing, or matching rules beyond the schema, so the 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?

Names the specific resource (one playbook) and the exact payload returned (its full Markdown), plus how it is addressed (by name). It also implicitly distinguishes itself from the sibling list_playbooks, which supplies the names, so an agent can tell the two apart without opening either schema.

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 phrase 'by name from list_playbooks' encodes the intended call sequence: enumerate first, then fetch. The three content categories (methodology, reference note, operating principles) help the agent judge whether fetching is worthwhile, but there is no explicit statement of when not to call it or what happens for an unknown name.

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