Export AdsTurbo prompt

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

With no annotations, the description carries full responsibility for behavioral disclosure. It explicitly states the tool does not call the AdsTurbo API, which is a key trait. However, it omits details such as whether it validates inputs, performs any transformation, or what the output format is (e.g., it likely returns a string but is not stated).

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 very concise, consisting of two sentences with no extraneous words. The first sentence immediately states the purpose, and the second adds a critical behavioral note. Every word earns its place.

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 10 parameters and no output schema, the description should clarify the return type. It mentions the output can be pasted into AdsTurbo, implying a string, but it does not explicitly state the return format. The parameter descriptions are complete, so the overall completeness is adequate but not exhaustive.

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 100%, so the schema already describes all parameters adequately. The description does not add any additional context beyond what the schema provides, so it meets the baseline of 3.

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 it exports a video generation prompt for AdsTurbo, distinguishing it from sibling tools that generate ad content like briefs, scripts, or hooks. It also clarifies that it does not call the AdsTurbo API, hinting at its role as a local formatting tool. However, the verb 'export' is slightly vague compared to more specific verbs like 'generate' or 'format'.

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 implies use when a prompt for AdsTurbo is needed, but it does not explicitly state when to use this tool versus alternatives like generate_hooks or write_ugc_script. No guidance on prerequisites or when not to use it is provided.

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