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

Annotations already declare readOnlyHint=true and destructiveHint=false, which the description reinforces with 'Read-only, free.' Beyond that, the description adds behavioral context about the content (reusable strategy cards) and its relationship to the web app's Playbooks tab. It doesn't mention pagination or response format, but given the annotation coverage and the nature of a list tool, the description provides adequate transparency without contradiction.

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?

The description is a single paragraph but well-organized: first defines what playbooks are, then connects to the web app, then gives a usage rationale, and ends with 'Read-only, free.' Each sentence earns its place, though it could be slightly more concise without losing meaning. No unnecessary filler.

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 that tool has no output schema, 2 simple parameters, and read-only annotations, the description covers the essential context: what the tool returns (list of playbooks), why it matters, and that it is safe. It doesn't describe the return fields in detail, but for a list endpoint with optional parameters, this is reasonably complete. The only missing piece is pagination behavior, which is minor.

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?

Both parameters (full, limit) are fully documented in the schema with descriptions, achieving 100% schema coverage. The description itself does not reference parameters, so it adds no additional semantic value. Per the rubric, baseline 3 is appropriate when the schema carries the full explanatory burden.

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 ('List') tied to a distinct resource ('PLAYBOOKS saved in this workspace') and elaborates on what playbooks are, clearly distinguishing them from other list_* siblings like list_hooks or list_library. It is not a tautology and provides concrete, domain-specific meaning.

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 gives a clear usage context: 'Read one before planning an ad so you re-run what already worked instead of starting cold.' While it doesn't explicitly contrast with alternative tools (e.g., list_hooks, mine_angles), the guidance is actionable and helps an agent decide when to call this tool. The absence of explicit 'when not to use' is a minor gap, so 4 rather than 5.

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