szlcsc_search

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

With no annotations, the description carries full behavioral disclosure burden. It explains that missing price/inventory remain 'unknown' rather than '0', which is useful. However, it does not disclose read-only status, pagination, or sorting behavior inherent to the sort parameter. Adequate but incomplete.

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 short sentences, no extraneous content, front-loaded with the core action. However, the first sentence is in Chinese which may reduce clarity for non-Chinese agents; still, it is efficiently structured.

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?

Despite 9 parameters and a complex search tool, the description omits all filtering capabilities (sort, brand, package, stock, price, category). The existence of an output schema does not excuse the lack of guidance on parameter usage. Minimal coverage for a tool of this complexity.

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 0% for 9 parameters, yet the description offers no explanation for any parameter (query, sort, brand, package, etc.). The agent must infer meaning solely from parameter names, which is insufficient for correct invocation. Description fails to compensate for the lack of schema descriptions.

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?

Description clearly states 'search LCSC components, supplement inventory and pricing' which identifies the verb (search) and resource (components). However, it does not differentiate from siblings like szlcsc_parametric_search or szlcsc_get_part, missing explicit distinctions.

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?

Description provides no guidance on when to use this tool versus alternatives such as szlcsc_parametric_search or szlcsc_get_part. No when-to-use or when-not-to-use context is given; only a behavioral note on missing data.

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