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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, covering the safety profile. The description adds value beyond that by disclosing what the fetched playbook contains: the procedure, expected tool calls, and required answer fields. This gives the agent a clearer behavioral model of the return value.

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, front-loaded sentence that leads with the action and resource, then adds the key content distinctions. Every word earns its place, and there is no repetition of schema or annotation information.

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?

With no output schema, the description has to convey what the response will contain, and it does so by listing procedure, expected tools, and answer requirements. It is complete enough for a simple read operation, though it leaves out any explanation of the 'job' in the title and exact response formatting.

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 description coverage is 100%, so the baseline is 3. The description itself adds no parameter-specific meaning, but the schema already documents workflow_id and session clearly, including examples and the context for session. No compensation is needed.

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 and resource ('Get one playbook in full') and enumerates the meaningful contents of what is returned: the procedure, the tools to call, and what the answer must carry. This clearly distinguishes it from sibling list_workflows and search tools by indicating a single, detailed fetch.

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 the tool should be used when a full single playbook is needed, but it does not explicitly say when to prefer it over list_workflows or other siblings. There are no exclusions or alternative-selection conditions stated, so usage guidance is only implicit.

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