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

Annotations give readOnlyHint=false and openWorldHint=true, so the safety profile is partially covered. The description usefully discloses that the call makes a single attempt with no retry and no auto-pagination, and that provider fields/units must be preserved verbatim — real behavioral facts beyond the annotations. It still says nothing about rate limits, result richness, or what an empty/error response 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?

Three short sentences, front-loaded with the resource and then the operational constraints; nothing is padded. The first sentence is wasted repetition of the name, which keeps it out of the top band.

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 is thin: it never says what a result record contains (ad id, GMV, views, spark-ad flags), how paging interacts with the pageSize cap of 10, or that results must be re-requested manually. An agent knows how not to retry, but not what it will get back.

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 all 14 parameters are already documented (page, pageSize, sort pattern, country enum, min/max filters). The description's "preserve provider fields and metric units" reinforces that gmv/views/days values are in provider units, but adds no per-parameter detail. Baseline 3 is appropriate.

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?

"TikTok Ad Search" merely restates the tool name and title; it adds no specific scope (ad-level? creative-level? which metrics?). Nothing distinguishes it from siblings like nexscope_chuhaijiang_tiktok_ad_detail or nexscope_chuhaijiang_tiktok_creative_search, which an agent could easily confuse with it.

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 when-to-use guidance. There is no statement of when to pick this over the ad detail or creative search siblings, or what prerequisite data (e.g., a keyword or category) makes it appropriate.

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