Research TikTok ads

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

The readOnlyHint annotation already establishes this is a safe read operation, lowering the burden on the description. The description adds the narrow scope (brand or topic) but says nothing about result volume, rate limits, pagination, or what a returned ad looks like.

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?

A single, front-loaded sentence with no filler, and the verb+resource come first. It is efficient, though it is arguably too terse given the missing routing guidance.

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 read-only, parameterless research tool with no output schema, the description should at least convey how results are scoped and how it differs from get_brand_ads/search_ads. As written it is functional but leaves the agent guessing at result shape and boundaries.

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?

With zero declared parameters, the baseline is 4. The description mentions "a brand or a topic" as the search subject, which is the only signal about input, but the schema exposes no fields at all despite additionalProperties being true, so no further semantics are needed.

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?

States a concrete verb ("Find") and resource ("TikTok ads") with a clear scope ("for a brand or a topic"). However, it does not distinguish itself from the closely related siblings get_brand_ads and search_ads, which sound like they retrieve the same thing.

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?

There is no guidance on when to prefer this over get_brand_ads or search_ads, nor any exclusions or prerequisites. The only hint is the word "research" in the name, leaving the agent to guess the boundary.

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