jlcpcb_official_component_feed

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

With no annotations provided, the description carries the full burden and does well: it discloses authentication requirements, cursor-based pagination, and the need to reuse the returned lastKey. It does not detail rate limits or failure behavior, but the core behavioral traits are clearly stated.

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 tightly worded sentences that front-load the official/authenticated identity and then immediately explain the pagination mechanism. Every phrase earns its place with no wasted words.

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?

The description gives enough context to select and start using the tool: it names the output domain (component catalog), explains paging, and notes credentials. It stops short of describing the item fields or page shape, but for a bulk feed without an output schema this is a reasonable level of detail.

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 schema already covers the single parameter at 100% coverage, including the 'omit for the first page' instruction. The description reinforces the cursor reuse behavior and adds the 'entire library' context, but provides little new semantic information beyond the schema.

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 immediately identifies this as an authenticated, cursor-paginated bulk feed of the JLCPCB component catalog. It provides a specific action—page through the entire library—and distinguishes itself from detail/lookup tools by emphasizing full-catalog bulk retrieval.

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?

It states the prerequisite of API credentials and describes the intended use case of iterating the full catalog. However, it does not explicitly contrast with sibling tools like jlcpcb_official_component_library or jlcpcb_search_components, nor does it explain when not to use this tool.

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