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

Annotations already declare readOnlyHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds only the cryptic note that "missing and null fields remain unchanged" and that monetary values keep their original unit/type, without saying what that implies for paging limits, coverage gaps, or freshness of the ranking snapshot.

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?

Roughly two-thirds of the text is a flat dump of ~20 snake_case field names that pushes the actual purpose to the background and is not front-loaded. The sentences that remain are low-information.

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 field list does partially compensate for return-shape ambiguity, but for an 8-parameter ranking tool with required country/date/granularity it omits what makes a record rank, how to select sort fields from the known list, and how this differs from its sibling rankings tools.

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 carries parameter semantics and baseline 3 applies. The description does not explain how the listed row fields relate to the provider sort field (the schema default is total_gmv:desc, yet no such field appears in the enumerated list), which would have been genuinely additive.

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 opening sentence, "Provider business records for TikTok Creator Commercial," essentially restates the title and never states the action (list/rank creators) or the ranking semantics implied by date, country and granularity. It is indistinguishable from siblings like nexscope_chuhaijiang_tiktok_creator_rankings_growth and _agencies, which share the same framing. Only the enumerated row fields hint that this is a GMV/follower-metric creator leaderboard.

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 growth or agencies ranking variants, nor on prerequisites such as valid market/date combinations. An agent must infer everything from the schema alone.

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