Run Playbook

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

With no annotations, description fully carries behavioral disclosure. Explains that preflight_only inspects without executing, normal mode creates tasks and returns external actions, and response includes connector requirements. Clearly a mutating tool with side effects.

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?

Every sentence adds value: defines tool, two modes, post-run instructions. No fluff, efficient structure with important warnings front-loaded.

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 5 parameters, no output schema, and many siblings, the description covers workflow (preflight check, execution, follow-up actions on external_actions and fallback_task). Implicitly explains return values. Minor gap: could specify structure of 'structured instructions'.

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 covers all 5 parameters with descriptions, so baseline is 3. Description reinforces preflight_only usage but doesn't add new semantic details beyond schema for other 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 clearly states 'Execute a playbook against a customer' with specific verb and resource, and distinguishes between preflight and normal modes. It uniquely identifies the tool's core function among siblings.

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?

Provides explicit instructions for preflight mode to inspect before committing, and for normal mode details post-run actions including handling external actions and fallback tasks. Lacks explicit exclusion of alternatives but context is clear.

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