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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered without the description. The description adds that results are curated failure modes plus fixes from a handbook, which is useful framing, but says nothing about result volume, ranking, or truncation behavior.

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 sentence that front-loads the return value and then the filter axes; every clause carries information and there is no padding or restatement of the tool name.

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 read-only lookup with no output schema and no required parameters, the description is close but leaves the most impactful unknown unanswered: what comes back when no filters are given, and whether the result set is bounded. Everything else an agent needs to form a call is present.

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 only 50%: slug and query are documented in the schema, while agent and playbook have no descriptions. The prose does name all four filters and clarifies that 'query' means the problem in plain words, giving it a semantic edge over the bare schema, but it never explains what an agent or playbook value actually looks like (name vs. ID).

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 known failure modes and their fixes from a named source (the Agents Handbook). It also enumerates the four filter dimensions, so an agent can tell what retrieves what. It stops short of distinguishing itself from siblings like get_playbook or search_playbooks, which is why it lands at 4 rather than 5.

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 filter list implies the situations in which the tool is useful (by agent, playbook, slug, or free-text problem), but there is no explicit when-to-use, when-not-to-use, or routing to an alternative sibling. Nothing states what happens when no filter is supplied, which is a real gap given zero required parameters.

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