Write UGC ad scripts

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

With no annotations, the description must disclose behavioral traits. It states it writes scripts and does not call AdsTurbo API, but fails to mention other important aspects such as generation approach, latency, cost, or whether it mutates state. The description adds little beyond the name and schema.

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 two sentences long, contains zero filler, and conveys the core purpose and a key constraint. Every sentence 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 18 parameters and no output schema, the description is too sparse. It does not explain the return format, pagination, or how the script content is structured beyond listing components. For a complex generation tool, this is insufficient preparation for correct 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?

The input schema covers 100% of parameters with descriptions, so the baseline is 3. The tool description mentions the output structure (hook, problem, etc.) but does not add meaning or context to any specific parameter beyond what the schema provides.

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 that the tool writes three UGC-style ad scripts with specific components (hook, problem, demo, proof, CTA, on-screen text, shot notes). It identifies the resource and action, but does not explicitly differentiate from sibling tools like generate_hooks or build_ad_brief, which produce related but distinct outputs.

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 includes 'No AdsTurbo API calls' which is a constraint, but provides no guidance on when to use this tool versus alternatives like build_ad_brief or generate_storyboard. There is no mention of prerequisites, typical use cases, or when not to use it.

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