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

No annotations are provided, so the description carries the full behavioral disclosure burden. It honestly states the credit cost, the free 24h-cache path, the default always-fresh behavior, and the policy that empty results and failures are not charged. It omits auth or rate-limit context but is still substantively transparent.

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 a single, efficient sentence with no filler. It front-loads the resource, then packs in the cost, cache option, and free-failure/empty behavior in a compact, readable way.

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 5-parameter search tool with 100% schema coverage and no output schema, the description adequately covers cost, caching, result-filtering behavior, and default freshness. It doesn't spell out the response payload structure beyond 'uniform null schema,' but that is a minor omission for this kind of search endpoint.

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?

The input schema already covers 100% of parameters with descriptive detail, so the baseline is 3. The description adds the idea of 'relevance-filtered,' which gives extra meaning to q, but otherwise the schema does most of the parameter-documentation work.

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 clearly identifies the tool as 'Search TikTok Commercial Content Library,' with a specific verb and resource, and adds that results are relevance-filtered with a uniform schema. It does not explicitly differentiate from sibling tools such as tiktok_ad_library_ad_details or tiktok_library_top_ads, but the verb+resource makes the search role apparent.

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 provides operational guidance (2-costs, cache=true, empty/failures never charged) but gives no explicit statement about when to use this tool versus siblings like tiktok_ad_library_top_ads or tiktok_ad_library_ad_details. There is no when/not-when or alternative routing, leaving the choice to inference.

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