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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds real value by revealing the return payload structure (summary, checkpoints, prompt variant, steps with checks, failure modes, evidence links, success rate) and that the prompt is variant-dependent on the agent parameter.

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 dense sentence that front-loads the return content, with zero filler. It is long but every clause corresponds to an actual output section, so it earns its length.

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?

No output schema exists, so the description carries the burden of describing returns, which it does thoroughly via the section enumeration. Only minor gaps remain, such as size/format assumptions around the markdown body.

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 description coverage is 100%, so the schema already fully documents all three parameters, establishing a baseline of 3. The description only lightly reinforces the agent-dependent prompt variant and does not add format or syntax detail beyond what the schema provides.

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?

States a specific verb and resource ('Returns one Agents Handbook playbook') and enumerates the markdown sections returned. The singular 'one' plus the required slug implicitly separates it from search_playbooks, though the sibling is never named in the description itself.

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?

Usage is only implied: the required slug parameter (documented in the schema, not the description) signals this is a single-item fetch following a search. There is no explicit when-to-use statement, no mention of search_playbooks as the discovery path, and no exclusions.

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