run_automation

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

With no annotations provided, the description carries the full burden. It discloses that the run is asynchronous (via polling instructions), that it does not affect the cron schedule, and that 'mode' can produce a video or draft only. It does not mention potential side effects like cost or permission requirements, but covers key behavioral traits.

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 well-structured and efficient: a clear opening statement, a key behavioral caveat, a practical polling tip, and a concise parameter list. Every sentence adds value without 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?

For a trigger tool with no output schema and no annotations, the description fully equips the agent: it explains the action, the non-effect on schedules, how to locate the resulting video, and the meaning of each parameter. Nothing critical is missing for successful invocation.

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?

Despite 0% schema description coverage, the description explains all three parameters: automation_id is the UUID, hook overrides the hook/topic, and mode specifies 'export' vs 'draft_only'. This adds substantial meaning beyond the bare schema types and defaults.

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 triggers a one-off slideshow generation using saved settings, with specific verb 'Trigger' and resource. It distinguishes itself from schedule-related tools by noting it does not affect the cron schedule, and from synchronous generation tools by describing polling behavior.

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 clear context by stating 'Does not affect the cron schedule', implying when to use this tool vs. schedule modifications, and gives a polling workflow for retrieving the result. However, it does not explicitly name alternative tools (e.g., generate_slideshow or update_automation), only implied exclusions.

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