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

Beyond the readOnlyHint and openWorldHint annotations, the description discloses meaningful behavior: duplicate results are preserved, media links are temporary, and each successful page including an empty page costs 0.2 credits. This is exactly the kind of non-obvious behavior an agent needs to know.

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 short sentences, each adding distinct information: purpose, pagination, duplicate behavior, media link behavior, and cost. The most important action is front-loaded and there is no filler.

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?

For a paginated search tool with no output schema, the description covers what matters: how to start, how to continue, what to expect regarding duplicates and media links, and the cost side effect. An agent has enough to invoke and paginate correctly.

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?

The input schema has no property descriptions, so the description carries the semantic burden. It explains that query must remain the same across pages and that cursor is used for continuation via next_cursor. This adds useful meaning beyond the raw schema constraints.

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?

The description states a specific action and resource: 'Fetch one relevance-ordered page of TikTok videos.' The term 'relevance-ordered' and the required query parameter make it clear this is a search-style tool, but it does not explicitly distinguish itself from siblings like get_tiktok_videos or list_tiktok_hashtag_videos.

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 description gives clear pagination guidance: 'Continue with next_cursor and the same query.' This tells an agent how to retrieve multiple pages. It does not explicitly name alternatives or when-not-to-use conditions, but the context establishes it as the tool for query-based TikTok video search.

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