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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds genuinely useful operational context that the annotations do not: no automatic retries and no automatic pagination, meaning the agent must page manually. 'Preserve provider fields and metric units' hints at passthrough semantics but is vague and never explains what the response looks like or what limits apply.

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 and free of padding. The first sentence is largely redundant with the title, and 'Preserve provider fields and metric units' is an imprecise instruction, but there is no bloat to trim.

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?

This is a 16-parameter, open-world search tool with no output schema, yet the description says nothing about result shape, what 'preserve provider fields' actually prohibits, or how page/pageSize interact with the no-auto-pagination rule. Only the required country parameter hint exists in the schema. For a tool this wide, the description leaves too much to inference.

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 16 parameters are already documented in the schema, which sets the baseline at 3. The description contributes no parameter-level meaning beyond that (it never mentions country, keyword, sort, pageSize, or the metric filters). Baseline is appropriate but no added value.

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 opening sentence 'TikTok Video Keyword Search' restates the title and the tool name almost verbatim, giving only the minimal implication that it searches TikTok videos by keyword. It does not distinguish this tool from the many near-identical siblings such as nexscope_tiktok_video_search, nexscope_chuhaijiang_tiktok_video_related_videos, or nexscope_tiktok_video_analytics. Purpose is inferable but never stated as a specific verb+resource with scope.

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 statement of when to use this tool, when not to, or which sibling to prefer for a related need. 'Execute only this operation' is an operational constraint on execution, not guidance on tool selection. An agent must guess between this and the ~10 other TikTok video tools.

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