jlcpcb_official_get_component_detail

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

No annotations are provided, so the description carries the burden. It discloses authentication requirements and the authoritative/more-complete nature of the data, which is valuable context. It does not mention rate limits or side effects, but the 'get' action and lack of mutation cues suggest a non-destructive read; considering the explicit auth and data-quality disclosure, it covers key behavioral aspects.

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 description is two sentences long, front-loads the official API context and purpose, and contains no filler. Every phrase contributes meaning, making it highly concise and well-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?

Given the tool's simplicity (one parameter, no output schema, no annotations), the description provides a solid context: it names the input, enumerates the fields returned, and highlights the authenticated/official nature. It omits response format details or error handling, but for a straightforward getter with a clear scope, this is sufficiently complete.

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% and the schema already documents the 'codes' parameter with an example. The description repeats that it accepts LCSC part codes and supports one or more, which largely mirrors the schema and adds minimal new semantic information. Thus, the baseline of 3 is appropriate.

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 clearly states the tool's function: fetching authoritative details (specs, stock, pricing, attributes) for one or more LCSC part codes. It uses specific verbs and resource, and the 'Official' prefix plus 'More complete than the public live endpoint' distinguishes it from sibling tools like jlcpcb_get_component_details.

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?

The description implies when to use this tool: when authenticated, authoritative, and more complete data is needed, explicitly comparing it to the public live endpoint. It notes the credential requirement, which acts as a prerequisite. However, it does not name specific alternatives or provide explicit 'when not to use' scenarios beyond the implicit comparison.

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