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

With no annotations provided, the description must carry the behavioral information. It discloses pagination behavior and token cost, which is helpful. However, it does not explicitly state that this is a read-only operation, nor does it detail rate limits or other side effects. Given the search nature, a 3 is appropriate for partial behavioral transparency.

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?

The description is four short sentences, front-loaded with the core purpose. Each sentence adds a distinct piece of information: purpose, required parameter, pagination, and cost. There is no wasted text.

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?

Given that an output schema exists and all parameters are documented in the schema, the description provides sufficient operational detail: keyword search, required query, pagination, and cost. It lacks explicit guidance on when not to use it, but the simplicity of the tool and schema coverage make it reasonably complete.

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 the schema already documents all parameters. The description only repeats that query is required and cursor is for pagination, which matches the schema. It adds minimal extra meaning beyond the schema, earning the baseline 3.

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 and resource: 'Search TikTok videos by keyword.' This clearly distinguishes it from sibling tools like tiktok.search_photos and tiktok.search_users, and the 'by keyword' qualifier specifies the search mechanism.

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 provides clear context for usage: it requires a query and explains how to paginate using a cursor. It does not explicitly exclude alternatives, but the focus on keyword search implicitly differentiates it from related tools like tiktok.for_you_feed. The cost disclosure is a useful practical guideline.

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