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

Annotations already declare readOnlyHint/openWorldHint/destructive=false, so the safety profile is covered. The description adds genuinely useful context: the token-based pagination model via nextPageToken, the fields returned per result type, and the embedded hasdataLink/hasdataPostsLink pointers.

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?

Front-loaded with the one-line purpose, then output shape, pagination, and use cases in sequence. It is on the longer side but each sentence carries distinct information, so little is wasted.

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, the description carries the return-value burden and does so by describing video vs user fields and the cross-links. Combined with full schema coverage and safety annotations, an agent has enough to call it correctly, though the sibling boundary remains implicit.

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 the enum, keyword, and nextPageToken semantics are already fully documented in the schema. The description only restates pagination at a high level, adding no syntax or format detail beyond what the schema provides; 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 clear verb+resource ('Searches TikTok by keyword') and enumerates the two result shapes (videos vs users) with their fields. It stops short of explicitly contrasting with the closely related siblings like hasdata_tiktok_profile or hasdata_tiktok_posts, though the hasdataLink/hasdataPostsLink mentions hint at the boundary.

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?

Provides concrete use cases: 'content discovery, trend research, influencer discovery, or building datasets from a keyword.' This gives clear positive context for when to reach for it, but names no alternatives or exclusions (e.g., when to prefer the profile or posts endpoints).

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