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 genuinely useful behavioral context beyond annotations: the privacy guarantee that 'the user's P&Ps and loan files stay in their own chat: never send their text to this server.' This is valuable operational transparency that the annotations do not convey.

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 paragraph with no filler. The purpose is front-loaded, followed by playbook enumeration, return-value description, and privacy note. Every sentence contributes information; it is slightly long but each clause earns its place.

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?

Given zero parameters and no output schema, the description carries the full burden of explaining return values, which it does thoroughly. It covers what playbooks exist, what the tool returns, the privacy constraint, and the id-based workflow—nothing an agent needs to call it correctly 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?

With zero parameters, there is nothing for the schema to document, so the baseline is 4. The description compensates by explaining the return payload (id, purpose, when-to-use, user requirements), which is meaningful context that helps the agent understand what the tool delivers.

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 states a specific verb and resource ('Lists the guided compliance playbooks this server runs in your chat') and enumerates exactly which playbooks are included (Fannie Mae LL-2026-04 P&P review, FHA/VA/USDA loan-file QC). It distinguishes itself from siblings like get_playbook_kit and start_playbook by clarifying it returns summaries and ids rather than executing anything.

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 explains that the tool returns 'each playbook's id, what it does, when to use it and what the user must provide', which serves as discovery guidance for choosing among siblings. It also states 'Playbook tools take only ids', implying this tool is the entry point for obtaining those ids. However, it does not explicitly name alternatives or state when NOT to use this tool.

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