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

Annotations already declare readOnly/openWorld/non-destructive, so the description earns credit for genuinely new behavior: the two-source fallback chain, identical response shape across sources, and null/empty/false semantics for fields TikTok doesn't expose. However, the cost statement is self-contradictory – 'at least 10 Nexscope credits' followed by '1 credit per request' – which is exactly the kind of disclosure an agent relies on for budgeting, so the value is undercut.

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 opening is well front-loaded, but the tail is vendor boilerplate: the tool name is echoed as 'TikTok Ad Library Ad Library Ad API View Pricing', the purpose is restated a second time ('Gets details for a TikTok ad from either...'), and two conflicting credit figures appear in the same paragraph. A reader must discard roughly half the text.

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 one-parameter, read-only, no-output-schema lookup, the essential operational facts are present: which sources are queried and in what order, that the shape is stable across sources, and how absent fields are represented. The only real gap is the muddled credit cost, which leaves an agent unable to predict spend.

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 single parameter already documents that it accepts a Top Ads material ID/URL or a public Ads Library ad ID/library.tiktok.com detail URL. The description only restates 'by ID or URL' and adds no format examples, validation rules, or failure modes for malformed input, so 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 first sentence states a specific verb and resource – 'Fetches one TikTok ad by ID or URL' – and the second names the two backing sources (Creative Center Top Ads, then Ads Library). It clearly reads as a single-item lookup versus the sibling list tool social_tiktok_ad_library_search, though that sibling is never named explicitly and the trailing 'TikTok Ad Library Ad Library Ad API View Pricing...' boilerplate dilutes the signal.

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?

The description implies the precondition (you must already hold an ad ID or URL), which tells an agent this is a detail call, not a discovery call. It never states the alternative path explicitly, e.g. 'use social_tiktok_ad_library_search to find ad IDs first'. The repeated-request/repurchase warning hints at caution but isn't framed as when-to-use guidance.

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