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

With annotations present, the description usefully adds that there is no automatic retry or pagination and that provider fields/metric units must be preserved verbatim. However, the annotations declare readOnlyHint=false for what appears to be a search, and the description offers no explanation of side effects or auth requirements, leaving that mismatch unaddressed.

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, front-loaded clauses with no wasted prose. The size is appropriate, though the leading clause is pure name repetition and earns little of its place.

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, open-world search with no output schema and only readOnly/openWorld annotations, the description says nothing about result contents, pagination limits, sort semantics, or how country affects results. An agent must infer far too much from the schema alone.

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 coverage is 100%, so the schema already documents all 15 parameters including sort format, pageSize bounds, and the preserve-units language. The description's 'Preserve provider fields and metric units' only echoes the schema's existing min/max metric notes, adding no new parameter meaning.

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 with 'TikTok Live Search', which merely restates the tool name and title rather than stating a verb+resource operation an agent can interpret. It never says what is being searched (livestreams/rooms) or what is returned, so it does not distinguish this from siblings like nexscope_chuhaijiang_tiktok_live_detail or nexscope_data_cj_lives_search.

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 execution constraint, not guidance on when to choose this tool over live_detail, live_related_products, or the CJ/KD livestream variants. No conditions, exclusions, or alternatives are named.

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