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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds one behavioral detail beyond the schema: pagination requires both cursor and search_id together. It does not mention anything about result volume, page-size limits, or what happens if only one pagination token is supplied.

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?

Two short sentences with the core purpose front-loaded and no filler. It is efficient, though it errs toward underspecification rather than being padded.

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?

An output schema exists, so return values need no explanation, and all four parameters are documented. What is missing is the disambiguation an agent needs when multiple TikTok search/effects tools exist, which is material given the very large sibling set.

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% and each parameter is documented in the schema, so the baseline is 3. The description's only addition is that cursor and search_id must be passed jointly, a marginal clarification over the schema rather than substantive parameter semantics.

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 effects'), which is clear enough to act on. However, it does not distinguish itself from nearby siblings such as tiktok_mobile_search or tiktok_mobile_trending_effects, so an agent must infer the difference.

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?

The second sentence gives explicit continuation guidance (pass both cursor and search_id from the prior response), which is genuine usage advice. But there is no statement of when to prefer this over tiktok_mobile_trending_effects or the general tiktok_mobile_search, leaving the main selection decision unaddressed.

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