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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=true. The description usefully adds no-retry/no-pagination behavior and the instruction to preserve provider fields and metric units, which the agent cannot infer from annotations. It stops short of describing result shape, ordering behavior of `sort`, or what happens at page boundaries.

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?

Three short sentences, front-loaded with the identity and then the two operative constraints. Nothing is padded, though the opening sentence is pure repetition of the title and earns little.

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 14-parameter, open-world search with no output schema, the description covers the pagination constraint but not what a result contains (ads with GMV/views/days metrics), how `sort` field names must be supplied, or what an agent should expect when provider-approved values are unenumerated. The rich schema compensates for parameters, so this sits at minimum viable rather than inadequate.

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 14 parameters is already documented in the schema (including the country enum and pageSize bounds). The description only adds the generic instruction to preserve metric units, which the schema already states per-field for minGmv/maxGmv/minViews/maxViews/minDays/maxDays. 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 description opens by restating the title ("TikTok Ad Search") with no verb/resource elaboration beyond that. It does not explain what an ad search returns or how it differs from adjacent siblings like nexscope_chuhaijiang_tiktok_creative_search or nexscope_chuhaijiang_tiktok_ad_detail. Purpose is implied by the name only.

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 only guidance is an operational constraint ("Execute only this operation; no automatic retries or pagination"), not a when-to-use rule. There is no indication of when to prefer this over sibling search tools (creative_search, product_search, video_search) or what market/keyword conditions make it appropriate.

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