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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds nothing beyond that: no mention of the pagination ceiling, the entitlement requirement for include_email, the default exclusion of inactive accounts, or the dataset's scope/coverage. For a 12-parameter dataset search, this is a thin behavioral disclosure.

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 with no wasted words, but at this brevity it is under-specified rather than genuinely concise for a tool with 12 parameters and rich filtering options. It neither misleads nor earns extra credit for structure.

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?

An output schema exists, so return values need not be described. But with 12 optional parameters, no enum hints, and only two minimal annotations, the description leaves an agent without the operational context (filters available, sort trade-offs, pagination cap) needed to call this well — context that the schema carries but the description should at least signal.

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 fully documents all 12 parameters including sort semantics, page limits, and the include_email entitlement rule. The description contributes zero parameter information, so the baseline 3 for high schema coverage applies rather than a higher score.

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?

States a clear verb ('Search') and resource ('TikTok creators dataset'), so the agent knows the general operation. However, it does not differentiate this tool from the many sibling dataset searches (datasets_youtube_creators_search, datasets_instagram_users_search, datasets_x_users_search), nor does it indicate what kind of query the dataset supports beyond the platform name. This is essentially the tool name restated with a platform label.

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?

There is no when-to-use guidance, no mention of alternatives (e.g., exact handle lookup vs full-text query, which the schema itself distinguishes), and no exclusions or prerequisites. An agent must infer everything from the parameter names alone.

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