execute_playbook

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

Annotations already indicate it's a mutable, non-idempotent, non-destructive operation. The description adds the behavioral context of step-by-step execution with result passing through context, and the dry_run capability. No contradictions with annotations.

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 sentence that conveys the core purpose, prerequisite, and a key feature. It is concise and front-loaded, though it could be slightly more structured with bullet points for clarity.

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?

The tool has a complex nested input schema but no output schema. The description explains the execution flow but does not mention return values, error handling, or limitations. Given the complexity and lack of output schema, the description is incomplete for an agent to fully understand the tool's behavior.

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 schema already documents the three parameters. The description only hints at context and dry_run implicitly without adding new semantic meaning beyond what the schema provides. Baseline score 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 verb 'Execute' and the resource 'playbook', specifying the step-by-step execution with context passing. It distinguishes from siblings like create_playbook or list_playbooks by focusing on execution. The mention of 'requires NOW_ASSIST_ENABLED' and 'Supports dry_run' adds specificity.

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 includes a prerequisite (NOW_ASSIST_ENABLED) and mentions dry_run as a feature, but it does not explicitly state when to use this tool versus alternatives like trigger_agentic_playbook or create_playbook. No explicit when-not-to-use or exclusions are provided.

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