tiktok get ads

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint false. The description adds a list of returned fields but no behavioral context beyond that, such as pagination behavior, rate limits, auth needs, or caveats about operation status or data scope. It does not contradict the annotations.

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 states the operation and the primary return contents, making it appropriately sized and easy to parse.

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 simple read-only listing tool with full schema coverage, an output schema, and clear annotation hints, the description plus structured metadata is sufficient for correct invocation. It is slightly incomplete in not mentioning filter behavior or alternative sibling tools, but those gaps are partly covered by the schema and purpose clarity.

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 100%, so the baseline is 3. The description adds no additional meaning beyond what the schema already provides for advertiserId, adgroupId, and limit.

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 uses a specific verb and resource ('List ads for a TikTok advertiser') and clarifies returned fields (ad ID, name, operation status, creative info). It is clear enough to distinguish ads from campaigns or ad groups, though it does not explicitly contrast with siblings such as tiktok_get_creatives or tiktok_get_adgroups.

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 gives no guidance on when to prefer this tool over alternatives, no exclusions, and no mention of using adgroupId to narrow results. It only implies usage through the tool name and the phrase 'for a TikTok advertiser,' which is insufficient among many sibling list/get tools.

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