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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so safety is covered. The description adds genuinely new behavioral context — single-shot execution with no retries or pagination, and a requirement to preserve provider fields and metric units verbatim — but says nothing about response shape or data freshness.

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 sentences with no filler, but the first sentence duplicates the title and carries zero information. The two remaining clauses are efficient but too terse to serve as a definition.

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?

There is no output schema, yet the description never indicates what a creative record contains or what the analysis/embedding expansions return. Combined with a tautological purpose line, an agent cannot tell from the description what it will get back or how this differs from the creative search sibling.

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%: id, country (15-value enum) and include (analysis/embedding expansions) are each documented in the schema, including the caveat that returned country_code may differ from the requested market. The description contributes nothing parameter-specific, so the baseline 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 only statement of purpose is "TikTok Creative Detail," which merely restates the tool name and title as a noun phrase. It never says the tool fetches a single creative record by ID, and it does not distinguish itself from the sibling nexscope_chuhaijiang_tiktok_creative_search (search vs. detail lookup). An agent must infer the verb and resource.

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 pick this tool over creative_search or the other TikTok detail tools. The only routing hint (that the ID comes from a search operation) lives in the schema's id description, not the tool description.

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