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

Annotations declare readOnlyHint=false and openWorldHint=true, but the description adds nothing about behavior, side effects, auth, or why a 'detail' endpoint is not read-only. It does not contradict the annotations, but it contributes no context beyond 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?

It is a single short sentence, but brevity here reflects under-specification rather than disciplined structure; it is essentially a restated title with no useful front-loaded information.

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 tool with no output schema, a non-read-only annotation, and two required parameters, the description should at minimum explain what the returned ad detail contains and how to obtain a valid id. None of that is present.

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, country (lowercase codes), and the optional include=core value. The description adds no parameter meaning of its own, 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 simply restates the tool title verbatim: "TikTok Commerce Intelligence CJ: ad creative/ads/detail API." It implies a lookup of ad detail for a given id, but offers no verb-level explanation of what the tool actually returns or how it differs from the many cj_* sibling tools.

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 prerequisites (e.g. needing an id obtained from nexscope_data_cj_ad_creative_ads_search), and no routing away from adjacent tools such as cj_ad_creative_ads_search or cj_ad_creative_ads_related_products. The word 'detail' only faintly implies a follow-up lookup.

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