jlcpcb_official_component_library

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

With no annotations, the description carries the full burden and does well by disclosing 'Requires API credentials' (auth needs) and 'paginated' (iteration behavior). It also implies a read-only operation via 'browse'. It does not detail response format or rate limits, but for a simple list tool this is solid coverage.

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 a single sentence that front-loads the core purpose ('browse the full assembly component library, paginated'), then adds necessary context ('Requires API credentials'). Every word earns its place; there is no fluff or repetition.

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?

For a simple two-parameter paginated list tool with no output schema, the description covers the essential context: the resource, pagination, and authentication. It lacks explicit alternative guidance, but that is a usage-consideration gap rather than a completeness gap for the tool's core function.

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?

The input schema already provides 100% description coverage for both page and page_size, so the schema does the heavy lifting. The description only mentions 'paginated,' which reinforces the parameter purpose but adds no new parameter-level semantics. Baseline 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 'browse[s] the full assembly component library' with a specific verb and resource, and adds 'paginated' and 'Official JLCPCB Parts API' context. This distinguishes it from siblings like jlcpcb_search_components (search) and jlcpcb_official_get_component_detail (detail), which focus on different operations.

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 provides context that the tool is authenticated and browses the full library, which implies use for enumerating components. However, it does not explicitly name alternatives or state when to prefer this over siblings like jlcpcb_search_components or jlcpcb_official_component_feed, leaving the guidance implicit rather than explicit.

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