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

Beyond the annotations, the description adds meaningful behavioral details: unknown profile fields are null, cursor pagination is opaque, and each successful page costs 0.2 credits. This helps the agent understand side effects and response semantics.

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 concise and well structured: three sentences that front-load the core action, then provide pagination behavior and cost. Every sentence contributes useful information.

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 an output schema, the description covers the essential operational details: one page per call, null unknown fields, cursor continuation, and credit cost. Nothing critical to invoking the tool correctly 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?

The schema has 0% description coverage, so the description must compensate. It clarifies that 'query' is the search input and that 'cursor' is an opaque pagination token via 'Continue with next_cursor.' However, it does not explain query formatting or cursor field details beyond this.

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 page of TikTok user search results.' This clearly distinguishes it from video search and profile retrieval tools, though it does not explicitly differentiate it from the sibling search_creators tool.

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 usage context for pagination: 'Continue with next_cursor and the same query; cursors are opaque.' It does not explicitly state when to prefer this tool over alternatives, but the intended use case is clear.

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