tiktok_mobile_live_search

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

No annotations are provided, so the description carries the full disclosure burden, and it does add real value by describing the response envelope (data entries of {type, anchor} with feedback_type=live, plus cursor and has_more) and the failure mode for a missing keyword. It stops short of noting auth needs, rate limits, or how cursor should be replayed for pagination.

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-loads the purpose in the first sentence, then adds scoping and response detail without filler. The backtick-laden envelope sentence is a bit dense but each clause carries information, and the 'first LIVE endpoint' note is minor padding.

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 reasonably compensates by naming the response fields and the required-keyword behavior. It is nearly complete for a two-parameter search, though pagination navigation and error/auth context would round it out.

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% (keyword and count are both documented in the schema), so the baseline is 3. The description slightly extends the keyword param by explaining the empty-envelope consequence of omitting it, but adds nothing about the count parameter's 0 = app default or max 50 semantics, which remain only in the schema.

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 and resource ('Search TikTok LIVE streams') and narrows scope to the mobile app's LIVE surface, which clearly separates it from tiktok_mobile_search (general search) and from the non-search live siblings like tiktok_mobile_live_effects and tiktok_mobile_live_gifts. An agent can route to it without opening a 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?

Implicitly conveys usage by specifying that keyword is required and that omitting it yields a 'valid but empty envelope,' which warns the agent not to call it without a keyword. However, it never states when to prefer this over tiktok_mobile_search or the other tiktok_mobile_* endpoints, so the selection guidance is left to inference.

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