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

With only readOnlyHint=false and openWorldHint=true in annotations, the description carries most of the disclosure burden, yet it adds little beyond boilerplate. The no-retry/no-pagination warning and the 'preserve provider fields and metric units' instruction hint at result handling, but nothing is said about what is returned, whether the call is billable, or how market-dependent fields behave.

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 short and front-loaded, which is good, but the second and third clauses are generic provider boilerplate that could be appended to any tool in this family. Brevity here reflects under-specification rather than disciplined editing.

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, so the description should describe the shape of an ad detail payload or at least its major sections, and it does not. For a lookup tool whose entire value is the returned record, the definition leaves the agent unable to predict what it will get back.

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 the schema already explains `id` provenance, the `country` enum semantics and the `include` expansion pattern, so baseline 3 applies. The description adds no parameter-level meaning beyond that, but it also does not mislead.

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 Ad Detail," which merely restates the tool name and title rather than stating a verb-plus-resource purpose. It never says the tool fetches the full record for a single ad identified by an ID, nor does it distinguish it from siblings such as nexscope_chuhaijiang_tiktok_ad_search or nexscope_chuhaijiang_tiktok_creative_detail.

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. There is no mention of the prerequisite that the required `id` comes from the ad search operation, and no statement of when a caller should prefer this over the related ad-search or related-products siblings.

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