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

Annotations declare readOnlyHint=false and openWorldHint=true, and the description adds nothing about cost, permission requirements, rate limits, or what is returned. It does not contradict the annotations, but it carries no behavioral information at all for a tool whose readOnlyHint=false is itself non-obvious for a data lookup.

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?

It is a single short sentence with no wasted words and is front-loaded, but it is under-specified rather than genuinely concise — the low length is achieved by omitting all substantive content.

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 description is the only place an agent could learn what a seller detail record contains or what the `include` facets (core vs channel) surface. It also never states that country+id uniquely identify a store. Only the schema's parameter docs partially compensate.

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%: id (store ID as string), country (lower case code), and include (core/channel or comma combination) are all documented in the schema. The description adds no meaning beyond that, so the baseline 3 applies.

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 is a restatement of the tool name and title ("sellers/detail API") with no verb describing what an agent actually gets back. It signals a seller-detail lookup by implication only, and does nothing to distinguish it from siblings like nexscope_data_cj_sellers_search or nexscope_data_cj_sellers_rankings_top_selling.

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, when-not-to-use, or alternative is mentioned. An agent cannot tell from this text whether to call this or nexscope_data_cj_sellers_search, nexscope_data_tiktok_seller_detail, or the related_* seller tools without opening schemas and guessing.

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