tiktok_get_ads

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

With no annotations supplied, the description carries the full burden of behavioral disclosure, but it only reports return fields. It does not address pagination semantics around the limit parameter, filtering behavior, rate limits, permissions, or what 'operation status' values look like; at best 'List' implies a read-only operation.

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 short sentences front-load the action and scope with zero filler. The return-field clause earns its place by previewing output, though it stays brief.

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?

Adequate for a simple 3-parameter list call: an agent can invoke it with just advertiserId and know the main output fields. But with no annotations and no output schema, the absence of pagination detail, the behavior of the adgroupId filter, and the meaning of 'operation status' leaves some inference required.

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 67% (advertiserId and adgroupId are documented); the description reinforces that the call is scoped to a single TikTok advertiser. However, the limit parameter is undocumented in both schema and description, and the description adds no filter or pagination meaning beyond what the schema already states.

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?

Names a specific verb ('List') and resource ('ads for a TikTok advertiser') and previews key return fields (ad ID, name, operation status, creative info). The entity level is clear enough to suggest a hierarchy position next to the campaigs/adgroups/creatives siblings, though 'creative info' is vag and overlaps conceptually with tiktok_get_creatives, and no explicit contrast is drawn.

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?

No guidance on when to use this versus the many list-type siblings (tiktok_get_campaigns, tiktok_get_adgroups, tiktok_get_creatives, tiktok_list_advertisers). The description just states what it does; any when-to-use signal is purely implied and no exclusions or alternatives are mentioned.

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