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

Annotations only declare readOnlyHint=false and openWorldHint=true; they give no cost, permission, or result-shape information. The description itself adds nothing about pagination limits (pageNumber max 5, pageSize max 100), whether results are ranked lists or summaries, or what the ranking metric is. Note readOnlyHint=false sits awkwardly against the verb 'Queries', though that reads more like an annotation mislabel than a description contradiction.

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 short sentence with no filler, and the scoping dimensions are front-loaded. It is efficient but so terse that the brevity shades into under-specification rather than crispness.

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?

Seven optional parameters, a nested sortField object, no output schema, and thin annotations mean the description carries substantial burden — yet it explains two dimensions and omits the ranking criterion, default sort behavior, and result contents. An agent would not know what it is actually ranking by or how to interpret a returned row.

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 already documents region, currency, language, pageSize, pageNumber, dateRange, and the opaque sortField object. The description merely echoes the region and date-range dimensions and adds no syntax, enum values for dateRange, or explanation of what sortField accepts. Baseline 3 applies when the schema does the heavy lifting.

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?

It names a verb ('Queries') and a resource ('creator rankings') plus two scoping dimensions, so the basic intent is legible. However, it gives no indication of what the ranking is based on (GMV, followers, growth) and does not distinguish it from near-identical siblings such as nexscope_tiktok_creator_analytics or the 'creators_rankings_growth/commercial/agencies' variants. An agent cannot confidently pick it out of that cluster from this sentence 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 when-to-use guidance, no exclusions, and no named alternative. The phrase 'by region and date range' implies one usage pattern but never states that this tool is for ranking lookups rather than creator profile lookups or keyword-based creator discovery.

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