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

With no annotations, the description carries the full burden and does substantial work: it discloses the nested return shape (item_list[].imagePost and the legacy search_item_list[].aweme_info.image_post_info.images path), notes that single-image posts are included, warns that image URLs can expire, and clarifies pagination state via has_more. Auth requirements and rate limits are still undisclosed.

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?

Purpose is front-loaded in the first sentence, followed by return shape, pagination, and caveats. The parenthetical legacy payload path is dense but earns its place for agents parsing raw responses; overall there is little waste.

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?

There is no output schema, so the description appropriately explains the return structure and image URL ordering/expiry, which an agent needs. It stops short of covering auth, rate limits, or explicit sibling routing, leaving minor gaps for a keyword-search tool.

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%, so all four parameters are already documented in the schema, including that search_id comes from log_pb.impr_id and is required when offset > 0. The description restates the offset/search_id workflow without adding syntax, format, or constraints beyond the schema, so the 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?

States a specific verb (Search) and resource (TikTok photo posts and slideshows) and implicitly separates itself from search_videos by restricting to photo posts/slideshows. It does not name a sibling alternative explicitly, so the agent must infer routing from the resource noun rather than being told.

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?

Gives concrete pagination guidance ('pass cursor as offset and log_pb.impr_id from the first page as search_id while has_more is true') and states scope exclusions ('No image downloading, OCR, analysis or aggregation'). It never names an alternative sibling such as search_videos or search_all for non-photo content, so the routing guidance is incomplete.

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