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

The annotation readOnlyHint=false sits in mild tension with a description that frames this purely as a retrieval ('Query ... retrieving'), though this is typical for external-API fetch tools so it is not a clear contradiction. The description usefully enumerates returned metrics (multi-period sales, GMV, followers, ratings, categories), which matters since no output schema exists. It says nothing about cost, rate limits, auth, or behavior when sellerId is invalid.

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 retrieval sentence is dense but front-loaded and informative. The trigger section is bloated with near-duplicate phrases ('TikTok seller detail' appears twice) and a long synonym list that pads rather than informs.

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 enumeration (sales periods, followers, rating, feedback/delivery/response rates, creator and video counts, price range, categories) is exactly the missing context an agent needs to judge relevance. Only error/invalid-ID behavior and cost remain unaddressed.

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 coverage is 100% and the schema already explains where to obtain sellerId and its max length. The description only restates 'by sellerId' and 'with a known sellerId', adding no format or validation detail beyond the schema.

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?

States a specific verb and resource ('Query TikTok Shop store (seller) details ... by sellerId') and enumerates the returned profile fields, so an agent knows exactly what data comes back. It does not explicitly differentiate itself from near-neighbours like nexscope_tiktok_shop_analytics or nexscope_data_et_seller_detail, which keeps it below a 5.

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?

Gives concrete trigger phrases and an important fallback rule — fire even when the user doesn't say 'Nexscope' or 'TikTok' if they want a full profile for a known sellerId. No when-not-use guidance or explicit alternative (e.g. search-first skills) appears in the description itself.

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