publish_video_via_automation

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

No annotations are provided, so the description carries the full burden. It discloses that the tool uses the automation's saved settings, that the video must be completed, and that post_mode defaults to the automation's setting. However, it does not mention reversibility, permissions, or response/error behavior, which is a gap for a mutating publish action.

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 compact and front-loaded, with a two-sentence overview followed by an Args list. No wasted words; every sentence adds information.

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 no annotations and no output schema, the description covers purpose, usage conditions, and parameter details. It lacks return-value or error-case information, but it is sufficient for an agent to select and invoke the tool correctly in most cases.

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%, but the description compensates by defining both parameters: video_id must be a completed video ID, and post_mode specifies DIRECT_POST or MEDIA_UPLOAD with TikTok draft semantics and default behavior. This adds meaningful guidance beyond the raw schema.

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 'Publish a completed video to TikTok using the automation's saved settings' with a specific verb and resource. It distinguishes from the sibling publish_to_tiktok by explicitly naming it as the standalone alternative.

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?

It explicitly states 'The video must be linked to an automation' and directs 'For standalone publishing, use publish_to_tiktok instead.' This provides a clear condition and alternative, satisfying when-to-use guidance.

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