execute_playbook

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

The description adds some behavioral context beyond annotations by explaining that results are passed forward in a step-by-step manner and that dry_run is supported. However, it doesn't disclose that executing a playbook will invoke other tools and may cause side effects, which is significant given readOnlyHint=false and openWorldHint=true. It also omits information about how errors are handled or what happens on actual (non-dry-run) execution.

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 conveys the core action, key behavior, a prerequisite, and a notable feature (dry_run). Every phrase earns its place with no fluff or redundancy.

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 the complexity of the playbook object and the absence of an output schema, the description is somewhat incomplete. It covers the primary purpose and important behavioral notes, but it doesn't explain execution semantics such as how steps invoke tools, how on_error and condition affect flow, or what the result format looks like. The schema provides detailed structure, but the description still leaves gaps for a complex orchestration tool.

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 parameters are already well-documented. The description adds minimal semantic value by correlating 'passing results forward' with the context parameter and highlighting dry_run support, but it doesn't provide new syntax or format details. Baseline 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 clearly states the tool's purpose with a specific verb ('Execute') and resource ('a playbook'), and adds how it works ('step by step, passing results forward through context'). It distinguishes itself from sibling tools like create_playbook and list_playbooks by focusing on execution, and from run_security_playbook by being general-purpose.

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 for executing a playbook and mentions a prerequisite ('requires NOW_ASSIST_ENABLED'), but it provides no explicit guidance on when to choose this over other automation tools (e.g., run_flow, trigger_flow) or when not to use it. No alternatives or exclusions are mentioned.

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