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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered. The description adds the useful cost signal '1 credit,' but stays silent on pagination behavior despite a cursor parameter and on result limits.

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?

Two compact sentences with the core action and the mode mapping front-loaded, and the credit cost appended. No filler or redundancy.

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?

With no output schema and a cursor-based pagination parameter, an agent lacks any statement about result shape or how to page. The essentials for invocation are present, but the definition is thin for a 4-parameter search tool.

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 0%, so the description must carry the load; it explains the search_type enum values, the most consequential parameter. It says nothing about query, count (max 100), or cursor semantics, so half the burden remains unmet.

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?

Names a specific verb (Search) and resource (TikTok creators/videos) and maps both search_type values inline, so the agent knows the two operating modes. It does not distinguish itself from siblings like tiktokUser or tiktokVideo, which fetch single entities.

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 parenthetical '(search_type: users) or (videos)' clarifies which mode to pick, which is the main usage decision. It gives no guidance on when to prefer this over tiktokUser/tiktokVideo or whether keyword search vs direct lookup is appropriate.

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