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

With no annotations provided, the description carries the behavioral burden. It discloses that the tool searches an adult-content domain and targets multiple content types, which is useful. It does not mention pagination, result ordering, or output shape, but the core read-only search behavior is clear enough for basic use.

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?

A single, front-loaded sentence that immediately states the action, source, content types, and search method. There is no filler or redundant repetition, and every word contributes meaning.

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 simple single-parameter search tool, the description is adequate for selecting and invoking the tool. The absence of an output schema and lack of detail about result structure or pagination leave minor gaps, but no essential invocation information is missing.

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% and the only parameter q is already documented as 'Search query'. The description's phrase 'by keyword' adds minimal semantic value, so the baseline of 3 is appropriate.

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 uses a specific verb ('Search'), names the resource ('tik-tok.porn'), and defines the scope ('adult videos, hashtags and creators') and method ('by keyword'). This clearly distinguishes it from sibling browse/list tools like get_feed, get_trending, list_creators, and list_tags.

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 implies usage when a user wants keyword-based discovery across videos, hashtags, or creators. However, it does not explicitly state when to prefer this over the sibling browsing tools, nor does it mention any exclusions or alternative conditions.

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