playbook_run_now

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

Annotations set readOnlyHint=false, consistent with the mutation implied by 'Run'. The description discloses that the tool returns a digest and saves it to the in-app inbox. No contradictions, but could elaborate on potential side effects or execution time.

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 followed by usage examples, with no wasted words. Information is front-loaded and easy to parse.

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 single parameter and no output schema, the description covers the core functionality: run a saved playbook and get a digest. It assumes the playbook exists but does not address error handling or prerequisites. Adequately complete for a simple operation.

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 coverage is 0%, so description must compensate. The description uses '<name>' in examples, clarifying that the parameter expects the playbook's name. This adds meaningful context beyond the bare schema, though it could specify naming conventions.

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 action ('Run a saved playbook'), the resource ('saved playbook'), and the output ('return its digest'). It distinguishes from sibling tools like playbook_create, playbook_list, and playbook_schedule.

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 provides explicit example phrases ('run my <name> playbook', 'check my brand watch now', 'run that workflow') indicating when to use. However, it lacks explicit exclusions or mention of alternatives for other actions like creating or scheduling.

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