create_automation

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

There are no annotations, so the description carries the full burden of behavioral disclosure. It mentions 'recurring' and 'generates and publishes' but does not disclose side effects such as whether creation immediately triggers publishing, whether it returns an automation ID, or what preconditions are required. For a mutation tool, this is a notable gap.

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: a single front-loaded purpose sentence followed by a compact parameter list. Every parameter line adds value without unnecessary prose, and the format makes information easy to scan.

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 tool has 9 parameters, no annotations, and no output schema, the description covers the core purpose and all parameter semantics. However, it omits the return value, potential immediate execution behavior, and prerequisites like having valid TikTok account/product references, so it is not fully complete.

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 description coverage is 0%, yet the description explains all 9 parameters with meaningful detail. It provides a concrete example for schedule, timezone information, source for tiktok_account_id, and clarifies nested object purposes like image_settings and tiktok_post_settings. This fully compensates for the lack of schema descriptions.

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 opens with a specific verb and resource: 'Create a recurring automation that generates and publishes slideshows to TikTok on a cron schedule.' This clearly defines the tool's function and distinguishes it from sibling tools like list_automations, get_automation, delete_automation, and run_automation.

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 clearly states the tool's purpose and cron scheduling context, but it does not explicitly contrast it with immediate-action tools like run_automation or publish_video_via_automation. Usage is implied rather than directly guided with alternatives or exclusions.

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