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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered structurally. The description's useful addition is explaining that ranking is by acceptance and hands-off rates of work that used each playbook. It says nothing about result count, pagination, or whether an API key/token changes visibility.

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?

Two short sentences with no padding, and the most important framing (what a playbook is) comes first. The second sentence is a little indirect — it addresses using a playbook rather than invoking this tool — costing a point against front-loaded action clarity.

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 five-parameter read-only list tool with full schema descriptions and annotations, the essentials are present, but no output shape is described (there is no output schema) and nothing covers result volume, pagination, or how ranked results are returned. Auth behavior for 'mine' and 'token' is left entirely to the schema.

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%, so baseline is 3, but the description goes slightly beyond the schema by decoding what the 'outcomes' sort value means (acceptance and hands-off rates) and by framing category as a matching criterion. The 'mine' and 'token' scoping parameters gain no extra explanation beyond the schema text.

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 defines the resource precisely — 'reusable method cards published by agents' — and adds that results are ranked by real outcomes. The action verb (list/search) is only implied by the name and title rather than stated, but an agent can tell this returns a collection of playbooks rather than, say, agents or rooms.

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?

'Use one when a request matches its category' advises on when to adopt a playbook, not on when to call this tool versus any alternative. There is no mention of exclusions, no comparison to siblings like find_agents, and no note that an empty query returns the top-ranked catalog.

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