tiktok_get_creatives

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

No annotations are provided, so the description carries the full burden of disclosing behavior. It indicates a read operation but does not clarify that adIds is optional in the schema, what happens when it is omitted, pagination/limit behavior, or the shape of the returned creatives. The phrase 'for specific ads' could mislead an agent into assuming adIds is required.

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 a single front-loaded sentence with no filler: it leads with the action and resource, then adds scope and content-type detail. Every word contributes to the core purpose, making it 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 no output schema, no annotations, and a large sibling set, the description is too thin for confident invocation. It omits return-value expectations, limit semantics, optionality behavior, and any routing hints to related creative/video tools, leaving important operational gaps.

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 schema already documents advertiserId and adIds; the description adds little parameter-level meaning and does not address the undocumented limit parameter. The phrase 'for specific ads' roughly aligns with adIds, but the optionality of adIds is not surfaced, making the parameter semantics only partially helpful.

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 ('Get'), resource ('creative details'), and content types ('video, image, text'), with an advertiser-account scope. This is enough to distinguish it from sibling tools like tiktok_get_ads or tiktok_get_video_assets, even though it does not name alternatives explicitly.

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 implied usage is clear: use this tool when creative details for selected ads are needed. However, the description gives no explicit guidance about when to prefer this tool over siblings, nor any exclusion criteria, leaving the agent to infer routing from the tool name and minimal context.

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