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

Annotations only declare readOnlyHint=false and openWorldHint=true, which is notable for a 'search' endpoint and begs explanation the description never gives (e.g. whether calls consume credits or hit a live external source). The description adds no behavioral context whatsoever beyond the title. It does not contradict the annotations, but it does nothing to illuminate them.

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 single sentence contains zero waste but also zero substance; it is under-specification rather than conciseness. There is nothing front-loaded because there is nothing to front-load.

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 7-parameter commerce-intelligence search tool with no output schema, the description should explain the data source, what a result contains, and payout/cost implications. Instead it offers a title echo, leaving the agent unable to predict results or decide between the many creator-related siblings.

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% and every parameter (country, keyword, category, sort, page, pageSize, hasContact) is documented inline with formats and limits. Per the baseline rule this yields a 3 even though the description contributes nothing about parameters — the schema does all the work.

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 is a restatement of the tool name and title: 'TikTok Commerce Intelligence CJ: creators/search API.' It conveys no more than the name already does — no statement of what is searched, what a creator record contains, or how it differs from siblings like nexscope_data_cj_creators_detail or nexscope_tiktok_creator_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?

There is no when-to-use guidance, no prerequisites, and no mention of alternatives. The agent is left to guess whether this or nexscope_data_cj_creators_detail, nexscope_chuhaijiang_tiktok_creator_search, or nexscope_tiktok_creator_search is the right entry point for finding creators.

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