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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds genuinely useful behavior notes — monetary values retain their original unit and runtime type, and missing/null fields are left unchanged — but says nothing about pagination limits, total counts, or how records are ordered.

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 opens with an awkward, verb-less fragment and then dumps 18 field names inline, which is informative but unstructured. 'Missing and null fields remain unchanged' is ambiguous filler that reads like a schema caveat rather than tool guidance.

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, the enumerated row fields partially compensate by telling the agent what to expect in the payload. However, the description omits what the ranking orders by default (schema shows gmv_30d:desc but the text doesn't confirm), the one-page/twenty-record cap, and any exclusion criteria, leaving meaningful gaps for a paginated ranking 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 100%, so parameters like country, page, pageSize and sort are already fully documented, giving a baseline of 3. The field list (e.g. follower_count, total_30d_video_live_gmv) implicitly reveals legal sort field names beyond the single schema example gmv_30d:desc, but that connection is never made explicit.

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 phrase 'Provider business records for TikTok Creator Agencies' identifies the resource (TikTok creator agencies) but never states a verb such as 'list' or 'rank', nor explains what the ranking is based on. It does not differentiate this tool from close siblings like nexscope_chuhaijiang_tiktok_creator_rankings_commercial or nexscope_chuhaijiang_tiktok_creator_rankings_growth, so an agent must infer the distinction from the name alone.

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 guidance on when to use this tool versus the commercial/growth ranking siblings, nor versus nexscope_chuhaijiang_tiktok_creator_search. The only contextual sentence ('Missing and null fields remain unchanged') describes output behavior, not invocation criteria.

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