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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds value beyond that by disclosing the pagination contract ('Keep returned cursor and has_more for bounded continuation') and a data-freshness caveat ('the page is a current discovery sample'), which are real behavioral traits not in the structured fields.

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 sentences, zero waste, with the core purpose front-loaded and the pagination note following. Efficient, though the second clause packs two ideas (cursor retention and sample nature) that could be slightly crisper.

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 the description covers the pagination loop an agent must implement. For a 2-param read-only discovery tool this is nearly complete; only the missing sibling differentiation keeps it from a 5.

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 both parameters (count, cursor) are already documented in the schema and the baseline is 3. The description reinforces the cursor's role in continuation but adds no syntax, default, or bounds information beyond what the schema provides.

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: 'Retrieve TikTok mobile's trending effect/sticker discovery feed with videos and sticker detail.' An agent can tell this is a trending-effects discovery feed rather than a live-effects or generic feed tool, though it never explicitly contrasts with the close siblings tiktok_mobile_live_effects or tiktok_trending.

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?

There is no when-to-use or when-not-to-use guidance and no named alternative, despite several overlapping siblings (tiktok_mobile_live_effects, tiktok_mobile_feed, tiktok_trending). The phrase 'the page is a current discovery sample' hints at the use case but does not route the agent among alternatives.

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