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 the external data source Kalodata and enumerates returned engagement and sales metrics, but it does not disclose rate limits, authentication needs, or pagination behavior beyond what the schema implies.

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?

The description is front-loaded with the primary search and detail capabilities and remains reasonably compact. The final trigger sentence repeats earlier trigger terms and could be tightened, but it does not obscure the core usage.

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 15-parameter combined search/detail tool with no output schema, the description covers both modes and lists the key returned metrics. However, it does not clarify how leaderboard search and videoId detail mode interact, does not explain the nested sortField object, and does not resolve overlap with dedicated sibling tools.

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 the schema documents all 15 parameters. The description reinforces region, currency, language, date range, and videoId usage, but leaves filters such as shop_id, creator_id, product_id, category_id, revenue_range, followers_range, ads_roas, pageNumber, pageSize, and sortField to the schema.

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 states specific verbs and resources: searching TikTok e-commerce trending promotional video leaderboards and querying detailed data for specific videos, including the metrics returned. It is clear what the tool does, but it does not distinguish this combined analytics tool from close siblings such as nexscope_tiktok_video_rank, nexscope_tiktok_video_search, and nexscope_tiktok_video_detail.

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?

Trigger conditions are explicit, naming TikTok video search, ranking, viral chart, detail, and analytics, and instructing use even when Kalodata is not mentioned. However, it gives no guidance on when to prefer this combined tool over the dedicated video rank/search/detail siblings.

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