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

The annotations already establish that this is a non-read-only, open-world, non-destructive operation. The description adds important behavior beyond that: the ad is created PAUSED by default, and turning it on requires the user's confirmation. It still does not explain dry_run behavior or permission requirements.

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?

Two sentences with no wasted words, front-loading the creation behavior and default paused state before the confirmation requirement. The structure makes the key operational facts 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?

For a 13-parameter create tool with low schema description coverage and no output schema, the description is too thin. It covers the creative composition and paused default but omits required identity parameters and dry_run semantics, leaving the agent without enough guidance to invoke it correctly.

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 only 31%, so the description needs to carry more parameter meaning. It clarifies the creative content fields (videos, texts, call to action, landing page or instant form), but leaves critical required parameters such as identity_id and identity_type, plus dry_run and name, unexplained.

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 states a specific verb and resource: create a PAUSED Smart+ ad in an existing ad group. It also names the required creative composition, so the agent can distinguish this from upload, status, or campaign-creation tools.

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 establishes a prerequisite that the ad group must already exist and notes that activation requires user confirmation. However, it does not name alternatives such as tiktok_upload_video for assets or tiktok_identities for identity IDs, nor does it state when not to use this tool.

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