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

No annotations are provided, so the description carries the full burden and largely meets it: it discloses the return shape (native data array with upstream result types and metadata), warns that entries are heterogeneous, and specifies the pagination loop condition (reuse cursor and log_pb.impr_id while has_more is true). It omits auth requirements and rate limits, which for an unannotated upstream-scraping endpoint would be useful.

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?

Four dense sentences, purpose front-loaded, and each one carries distinct information (scope, return caveat, pagination mechanics, sibling exclusion). It is slightly compressed — the pagination sentence packs two parameters and a loop condition — but there is no filler to cut.

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?

With no output schema and no annotations, the description still covers what an agent needs to call it correctly: what comes back (heterogeneous native array), how to paginate, and what it does not cover. Missing auth/permission expectations are the only notable gap for a network-backed 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 coverage is 100%, so the baseline is 3, but the description adds cross-parameter workflow meaning the schema does not: that the returned cursor and log_pb.impr_id must be fed back as search_id for continuation, and that this only applies while has_more is true. That is a genuine relationship between parameters, not a repeat of field docs.

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+resource ('Search TikTok's mixed-results endpoint in one request') and immediately distinguishes itself from the many search_* siblings by declaring that no separate creator, video, or sound searches are performed. An agent can tell this is the heterogeneous catch-all search rather than search_videos/search_users/search_sounds without reading any schema.

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 real usage context: use this for one mixed-results request, inspect entries rather than assume they are videos, and continue with cursor + log_pb.impr_id as search_id while has_more is true. It implies but never names the dedicated alternatives (search_videos, search_users, search_sounds), so routing is inferable but not explicit.

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