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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is covered. The description adds two genuinely new facts (no automatic retries, and that provider fields and metric units must be preserved verbatim), but the "no automatic pagination" note merely repeats the page parameter's own schema description, and nothing is said about failure modes, rate limits, or result shape.

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?

It is short and front-loaded, but the opening sentence is pure title repetition and consumes the highest-attention slot without conveying anything. The remaining sentences are terse operational rules rather than an explanation, so brevity here reflects under-specification as much as discipline.

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 nine-parameter, open-world, read-only search with no output schema, the description does not explain what a creative result contains, how keyword/category/boolean filters combine, or what the undocumented sort field space looks like. Combined with annotations covering only safety, an agent has almost no basis for predicting the response beyond the parameter names.

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 every one of the nine parameters already carries its own documentation (page, pageSize cap of 10, country enum, sort pattern, boolean flags). The description adds no additional parameter meaning, so the baseline 3 applies.

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 first sentence, "TikTok Creative Search," simply restates the tool name and title; there is no verb phrase describing the operation and no definition of what a "creative" record is. It is not distinguished from near neighbors such as nexscope_chuhaijiang_tiktok_ad_search, tiktok_creative_detail, or tiktok_video_search, so an agent cannot tell from this text which one to call.

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?

"Execute only this operation; no automatic retries or pagination" is an invocation directive, not a when-to-use rule. Nothing says when this search is preferred over the ad, video, or creator search siblings, nor what a caller should have ready (keyword vs. category vs. filters) before invoking it.

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