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

The description usefully enumerates what the detail mode returns (follower count, video/live revenue, GPM, contact info, associated shops), which goes beyond the schema. However, annotations declare readOnlyHint=false for what is described purely as search/query behavior, and the description never addresses this or explains pagination/limits beyond what params already state. No annotation contradiction is asserted since the description itself makes no mutating claim, but the mismatch is left unexplained.

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?

Purpose is correctly front-loaded, but the trigger list repeats the identical phrases twice verbatim ('TikTok creator search, TikTok creator ranking, TikTok influencer leaderboard, TikTok creator detail' appears twice), bloating the description without adding coverage. That redundancy costs real space in an otherwise two-sentence definition.

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 dual-mode tool with 14 optional parameters and no output schema, the description should more clearly frame that leaderboard and detail are effectively two operations sharing one schema. It names the detail fields but says nothing about what a leaderboard response contains, leaving the agent to discover result shape empirically.

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%, so all 14 parameters are already documented, including the rank-only scoping of pageSize/pageNumber. The description adds one genuinely useful mapping: creatorId switches to detail mode, and region/currency/language/dateRange apply to leaderboard ranking. That is incremental, not compensating, so baseline 3 applies.

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 first sentence names two concrete verbs and resources: searching TikTok creator leaderboards and querying detailed creator profiles, both via Kalodata. It also clarifies the mode switch using creatorId. It stops short of naming the obvious siblings (nexscope_tiktok_creator_search, nexscope_data_kd_creator_rank/creator_detail) that an agent would otherwise have to disambiguate by opening schemas.

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 trigger-phrase list and the 'even if the user does not explicitly mention kalodata' clause give the agent a clear activation context, but no when-not-to-use guidance and no named alternatives among the many overlapping TikTok creator tools. The choice between rank mode and detail mode is only implied by whether creatorId is supplied.

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