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

Annotations declare readOnlyHint=false and openWorldHint=true, and the description adds zero context about cost, rate limits, result size, or why a 'search' endpoint is flagged non-read-only. The full behavioral burden is unmet — nothing beyond the structured hints is disclosed.

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?

It is a single short sentence with no padding, but it is under-specified rather than concise — the brevity comes at the cost of conveying any information at all.

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 9-parameter, open-world search endpoint with no output schema, the description should explain what a creative record contains and how filters interact. It explains nothing, leaving the agent entirely dependent on the schema and name.

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 9 parameters (country, keyword, category, isAigc, hasProduct, isSponsored, sort, page, pageSize) are documented in the schema itself. The description contributes no additional meaning, so the baseline of 3 applies.

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 verbatim the tool title: 'TikTok Commerce Intelligence CJ: ad creative/creatives/search API.' It restates the name rather than explaining what the tool returns or does. It does nothing to distinguish this from sibling tools like nexscope_data_cj_ad_creative_ads_search, nexscope_data_cj_ad_creative_creatives_detail, or nexscope_chuhaijiang_tiktok_creative_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 mention of alternatives, and no conditions or prerequisites. An agent cannot tell from this text whether to call this versus the ads_search or creatives_detail siblings.

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