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

Annotations already declare readOnlyHint=true, openWorldHint=true, destructiveHint=false, so safety is covered. The description contributes genuine post-call semantics: absent/null fields stay unchanged and monetary values preserve original unit and runtime type. It says nothing about result volume, coverage per market, or whether the field list is exhaustive, which limits its added value.

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 tight sentences with no padding, and the field inventory is front-loaded where an agent would look for it. The first sentence is close to redundant with the tool name, which keeps it from a 5.

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 usefully enumerates known row fields and explains type/unit handling for prices, which is the right kind of compensation. It still omits expected result counts and whether the listed fields may be absent per record; minor for a read-only lookup tool with fully documented params.

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 both osKey and country are already fully documented with format, defaults and the upload prerequisite. The description adds no parameter-level meaning beyond the schema, which is the expected baseline when the schema does the work.

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 frames the tool as returning "business records for TikTok Product Image Search" and lists representative row fields, so the agent learns the resource is TikTok product records. However, the opening sentence largely restates the tool name, and nothing distinguishes it from the very similar siblings nexscope_chuhaijiang_tiktok_product_search or nexscope_data_cj_products_image_search. The verb (image-based lookup) is only inferable, not stated.

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 statement of when to use this versus tiktok_product_search or the other image-search siblings, and no prerequisites or exclusions. The only workflow hint (obtaining osKey via the upload flow) lives in the schema, not the description. An agent must infer the image-upload dependency entirely from parameter documentation.

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