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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=true, so the safety profile is covered. The description adds a data-fidelity note (missing/null fields unchanged, monetary values keep original unit and runtime type), which is useful context about returned values but stops short of disclosing ranking behavior, default ordering, or pagination 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 sentences, but the first is a near-tautology and the second is a long undifferentiated field dump that crowds out the more important scoping information. It is front-loaded with the least informative statement rather than the tool's purpose.

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 row-field list does useful work by previewing the response shape. However, for a paginated, sortable ranking endpoint with a three-parameter required core, the description omits what the ranking is ordered by, how granularity affects the growth interval, and pagination limits.

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 all eight parameters are already documented in the input schema; baseline 3 applies. The field list in the description describes return rows, not parameter semantics, so it adds nothing about country codes, granularity values, or the field:asc/desc sort grammar beyond what the schema states.

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?

"Provider business records for TikTok Creator Growth" largely restates the title, but the enumerated row fields (interval_new_follower, tioktok_creator_growth_interval_new_follower_ratio, follower_count) do reveal that this returns creator records with growth metrics. It never states that it is a *ranked* list, and it gives no basis for distinguishing it from siblings like nexscope_chuhaijiang_tiktok_creator_rankings_agencies or _commercial.

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 choose growth rankings over agencies/commercial rankings, or over the creator_search / creator_detail siblings. No prerequisites, no mention that country+date+granularity are mandatory to get a valid ranking.

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