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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered; the description adds genuinely new behavior: the visibility rule (teammates' private playbooks never appear) and the fact that only summaries are returned. It also adds a presentation constraint for link_url that affects output handling. It stops short of noting ordering, result caps, or empty-list behavior, which keeps it below a 5.

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?

Front-loaded with the core scope sentence, then usage, then output/link handling — a sensible ordering with no filler. The bolded 'Links:' block is formatted as an embedded instruction and is somewhat bulky relative to the rest, but it carries operationally relevant content rather than repetition.

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?

An output schema exists, so return values need not be spelled out, and the description still tells the agent that items require a follow-up get_playbook call. Combined with the visibility semantics and the pre-instantiate routing, an agent has enough to select and call it correctly; only minor operational details (ordering, whether the list can be empty) are unstated.

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 tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline is 4. The description correctly spends no words on inputs and instead redirects effort to scope and output expectations.

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 ('List all content playbooks') plus a precise visibility scope ('visible to the caller in the current team: team-visible plus the caller's own private ones, never a teammate's private'), and adds a definition of what a playbook is. It also distinguishes itself from get_playbook ('returns summaries only'), so an agent can separate it from its nearest sibling without opening any 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?

An explicit 'When to use' section covers both trigger classes: user intents ('what playbooks do I have', 'show my templates') and a prerequisite workflow step (before instantiate_playbook / update_playbook to find the right id). It names the alternative tool for detail retrieval, leaving little to inference.

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