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

Annotations declare readOnlyHint=false, which is counterintuitive for a ranking/query endpoint; the description does nothing to clarify why a read-style ranking call is flagged as non-read-only, nor does it disclose pagination limits (pageNumber 1-5, pageSize 5-100), rate limits, or auth requirements across 17 filter parameters. With zero behavioral context added, the description leaves the agent unable to reason about the tool's execution profile.

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 sentence that merely echoes the title is not concise so much as empty; every word is redundant with structured metadata and nothing is front-loaded about scope or return shape.

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 17-parameter ranking endpoint with no output schema, the description omits what ranked entities are returned, in what order, over what default time window, and how the many filters interact. An agent has essentially only the parameter names to infer behavior.

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 17 parameters (region, shop_id, video_id, dateRange, is_affiliate, revenue_range, etc.) are already documented in the schema. The description adds no meaning beyond that baseline, but it also doesn't need to compensate for gaps.

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 description restates the name and title verbatim ('TikTok Intelligence KD: product/rank API') without stating what data is returned, what the ranking means, or what market it covers. An agent cannot distinguish it from nexscope_data_kd_video_rank, nexscope_data_kd_creator_rank, or nexscope_data_kd_shop_rank beyond the word 'product'.

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?

No when-to-use guidance, no exclusions, and no mention of the obvious sibling alternatives for product lookups (nexscope_data_kd_product_detail) or other ranking endpoints. The only implicit signal is 'rank' in the name, which the agent must interpret on its own.

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