get_pm_playbook

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

The description implies the tool is read-only and non-destructive (it provides information), but with no annotations, it should disclose more about what it returns (e.g., the full playbook text). The description does not contradict any annotations since none are provided.

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 two sentences, front-loads the purpose, and contains no wasted words. Every sentence serves a clear function: stating what the tool does and when to use it.

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 no output schema, the description should mention the return format (e.g., 'returns the full playbook text'). It covers purpose and usage but omits what the tool actually returns to the agent. The description is adequate but incomplete for full context.

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 has no parameters, and schema description coverage is 100%. The description adds no parameter information, which is acceptable given zero parameters. Baseline for 0 params is 4.

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 clearly states the tool provides instructions on 'how to operate as a product manager on AIOProductOS', specifying the resource (the playbook) and its purpose. This distinguishes it from sibling tools, which are action-oriented (e.g., create_task, analyze_funnel).

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 explicitly tells when to use the tool: 'Read this before planning or prioritizing.' It provides clear context for appropriate use, though it does not explicitly mention when not to use it or list alternative tools.

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