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

Annotations already declare the safe read-only/idempotent profile, so the bar is lower, and the description still adds real behavioral content: the exact creative identifiers returned and the warning that the numeric prefix in an ad NAME is not a video_id. It omits pagination/result-limit behavior and what happens when advertiser_id is blank.

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?

Front-loads purpose and filter, then adds the downstream-reuse rationale in one dense but purposeful sentence. The mid-sentence capitalization of the creative-field sentence is slightly heavy, but no sentence is filler.

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?

Even though an output schema exists, the description usefully explains the key returned fields and their cross-tool contract with create_tiktok_ad, which is exactly what an agent needs for this workflow. Gaps remain around advertiser_id scope and default result volume.

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%, so the description must carry the parameters. It explains adgroup_id's filtering effect well but says nothing about advertiser_id (presumably the account scope), leaving half the parameters semantically undocumented.

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?

Opens with a specific verb+resource ("Lists TikTok ads") and immediately qualifies scope with the optional adgroup_id filter. It also distinguishes itself from sibling listers by naming the creative payload it uniquely returns and the create_tiktok_ad tool it feeds.

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?

Gives clear context: use the adgroup_id argument to narrow to one ad group, and use the returned creative fields to reuse a winning creative in another ad group via create_tiktok_ad. It does not, however, state when to prefer this over list_tiktok_adgroups or other ad-retrieval paths, so no explicit exclusion guidance.

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