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

With no annotations, the description carries the full behavioral burden and does so impressively: it discloses the 1-credit cost, no charge for empty results or failures, 24h cache semantics, and the fallback scraper behavior with timeout degradation. It also reveals deduplication behavior ('distinct creators') and the presence of isApproximate flags, neither of which is visible in the schema.

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 dense sentences front-load the core purpose before cost, cache, and fallback details, with no filler. Each clause carries operational value, though the telegraphic middle section is compact at the expense of slight readability.

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?

The description covers returned identifiers (id, secUid), isApproximate flags, cursor pagination, costs, failure behavior, and fallback — enough for an agent to invoke the tool correctly even without an output schema. The exact response envelope and the precise meaning of 'per-counter' are left implicit, which is a minor gap in an otherwise complete definition.

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 coverage is 100% and the schema already thoroughly documents q, cache, limit, cursor, and fallback including defaults and costs, so the description adds limited new parameter-level meaning. It does reinforce global cost and failure semantics and output characteristics, but those are more behavioral than parameter-specific. Baseline 3 is appropriate here.

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 opens with a specific verb and resource — 'Search TikTok users' — and immediately narrows scope with 'distinct creators only, id + secUid', distinguishing it from sibling tools that return posts, channel details, or suggestions. Pagination and output focus make the tool's purpose unambiguous.

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 establishes clear context: use this when you need to find TikTok creator accounts by query, and it explains caching, costs, and fallback behavior that affect invocation choices. It does not explicitly name sibling alternatives or state when not to use this tool, so it falls short of fully explicit routing guidance.

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