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

Annotations already indicate the operation is not read-only and not destructive, and the description adds the useful behavioral detail that the result is a digest that is also saved to the in-app inbox. It does not discuss duration, errors, or required permissions, but for this simple action the disclosed behavior is adequate.

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?

Two focused sentences. The first states the action and result, and the second gives practical usage triggers. Every sentence earns its place and the most important information is 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?

For a one-parameter tool with no output schema, the description covers the essential invocation details: what to run, what to supply, what will be returned, and a notable side effect. It could be more complete by explicitly contrasting with playbook_schedule for recurring runs, but nothing critical is missing for a correct immediate call.

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?

The schema only declares a required string 'name' with no description, so the main description must compensate. The examples ('run my <name> playbook') clarify that 'name' identifies an existing saved playbook, but the description does not define the parameter explicitly or mention matching/format requirements. With one simple parameter this is adequate but not rich.

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?

States a specific verb (Run), a clear resource (a saved playbook), and a concrete result (return its digest). The trigger-phrase examples distinguish this immediate-execution tool from scheduled variants like playbook_schedule, so an agent can identify its purpose without ambiguity.

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 trigger examples ('run my <name> playbook', 'check my brand watch now', 'run that workflow') that tell an agent when to invoke it. It does not explicitly say when not to use it or name alternatives such as playbook_schedule, so it falls just short of full guidance.

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