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

With no annotations supplied, the description does add real behavioral context by disclosing that charges and authorization are enforced by the OpenAny gateway. It says nothing, however, about result shape, pagination behavior (despite page/limit parameters), or rate limits, so the transparency burden for a 15-parameter endpoint is only partly met.

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 definition is short and front-loaded, but the opening line is a tautology that consumes the most prominent position. The second sentence earns its place; the first does not.

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 15-parameter search endpoint with no annotations and no output schema, the description leaves major gaps: what corpus is searched, whether any parameters are effectively required, what a result contains, and how paging terminates. Only the billing/authorization note is substantive.

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%, with every parameter including bilingual descriptions and enum-like value lists for like, ad_format, and objective, so the schema already handles semantics. The description adds no meaning about how filters combine, which are required for meaningful results, or how search_id relates to paging.

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?

"Search ads" merely restates the title, and the only other content concerns gateway billing rather than what is searched. It gives no indication of scope (keyword/industry/country filters) and does nothing to separate it from siblings such as tikhub_post_api_v1_tiktok_ads_get_top_contents_list or tikhub_post_api_v1_tiktok_ads_get_recommended_ads.

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?

No when-to-use or when-not-to-use guidance is present, and no alternative tool is named. The note about gateway credentials and charges describes billing/authorization mechanics, not the conditions under which an agent should pick this search endpoint over the other TikTok ads tools.

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