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

Annotations already declare readOnlyHint=false and openWorldHint=true. The description adds operationally relevant context that no automatic retries or pagination will occur and that provider fields/metric units should be preserved, but it does not explain permissions, rate limits, or what the detail response contains.

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 description is short and front-loaded, with three compact sentences and no filler. However, the first sentence merely repeats the tool title and does not earn its place as strongly as the execution constraints that follow.

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 detail-retrieval tool with no output schema, the definition does not explain what kind of creative details are returned or how this tool relates to the creative search/ad detail siblings. Schema coverage is strong, but the description is too thin to complete the agent's context for selecting and interpreting the call.

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 all three parameters are documented in the schema, including the creative id, country enum, and include expansion format. The description adds no parameter-level meaning beyond what the schema already provides, so the baseline of 3 is appropriate.

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 essentially restates the title/name: "TikTok Creative Detail." It does not state a specific verb beyond the word "Detail" and gives no scope or distinguishing detail versus siblings such as nexscope_chuhaijiang_tiktok_creative_search or nexscope_chuhaijiang_tiktok_ad_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?

It provides no when-to-use guidance and does not name alternatives. The sentence "Execute only this operation; no automatic retries or pagination" is an execution constraint, not guidance about when this tool is preferable to the creative search or ad detail tools.

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