get_playbook

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

No annotations are provided, so the description carries the full burden. It only uses the verb 'Retrieve' without disclosing behavior for nonexistent slugs, return format, authorization needs, or whether it errors or returns null. This is a significant gap for a tool with no annotation safety profile.

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, focused sentence with no filler words. Every word contributes to conveying the tool's purpose and key constraint (slug-based retrieval).

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?

As a simple one-parameter getter with no output schema, the description adequately identifies the resource type and lookup key. It does not specify return structure or error handling, but given the minimal complexity and clear verb, it is sufficiently complete for basic invocation.

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 input schema fully documents the 'name' parameter with a type, description, and example (100% coverage). The description's phrase 'by name (slug)' reiterates the schema without adding semantic value, so the baseline of 3 is appropriate.

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 uses a specific verb ('Retrieve') and clearly identifies the resource ('ClawSkills workflow playbook') and lookup method ('by name (slug)'). It distinguishes itself from siblings like list_playbooks and search_playbooks by focusing on retrieving a single specific playbook.

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 implies usage when you have the exact slug, but does not explicitly state when to use alternatives (e.g., search_playbooks if slug is unknown) or provide exclusions. There is no guidance on prerequisites or filtering.

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