get_playbook

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

The word 'read' clearly signals a read-only operation, and the listed content types define what kind of data is exposed. There is no mention of what happens if no playbook exists or how the response is structured, but for a zero-parameter, side-effect-free tool this is a minimal but adequate disclosure.

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?

One short, front-loaded sentence with a colon-separated list. Every word contributes either the operation or its scope, with no redundant 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?

For a simple zero-parameter read tool, this description tells an agent why to call it and what kind of data to expect in the response. It does not specify edge behavior like an absent playbook, but that is not essential for correct tool selection.

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 the input schema already fully documents the interface. The description adds meaning about the content returned, which is sufficient given the absence of parameters.

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 ('Read') and resource ('how the user works'), and enumerates the exact facets: approach, bug-fix style, communication preferences. This clearly distinguishes it from related read tools like get_agenda or get_commits, though it does not explicitly name a sibling for contrast.

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 use when an agent needs to understand the user's working style and preferences. However, it gives no explicit guidance on when to use this instead of get_context or update_playbook, leaving routing slightly to inference.

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