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

The description does add real behavioral information beyond the annotations: no automatic retries, no automatic pagination (caller must loop pages), and provider fields/metric units must be preserved. However, it says nothing about result contents, rate limits, or why readOnlyHint is false for what is nominally a search, leaving the safety profile unclear.

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?

Three short sentences with no padding, which is appropriately sized, but 'Execute only this operation' is vague boilerplate ('this operation' is never defined) and the most valuable constraint, the no-pagination loop requirement, is buried in the middle rather than front-loaded.

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 9-parameter, no-output-schema search tool sitting among dozens of near-identical TikTok search siblings, the description should define what a creative is, what the results contain, and how to page through them. Instead it offers only execution guardrails, so an agent must open the schema and guess at the resource semantics.

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 documented in-schema, including the sort pattern caveat and country_code mismatch note, so the schema carries the burden and baseline 3 applies. The description adds no parameter meaning of its own beyond the generic 'preserve provider fields and metric units' remark.

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 opens with 'TikTok Creative Search,' which is a verbatim restatement of the tool title/name and adds no distinguishing detail. With nine sibling search tools (tiktok_ad_search, tiktok_video_search, tiktok_creative_detail, tiktok_product_search), the agent learns nothing about what a 'creative' search returns or how it differs from ad or video search.

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?

'Execute only this operation; no automatic retries or pagination' is an execution constraint, not usage guidance. There is no statement of when to choose this over tiktok_ad_search, tiktok_video_search, or tiktok_creative_detail, and no prerequisites or exclusions are given.

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