jlcpcb_refresh_database

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

Without annotations, the description carries the full burden of disclosure. It transparently mentions the ~50MB download and several-minute duration, giving the agent essential cost/side-effect information. It doesn't discuss whether existing data is replaced during the rebuild, but the term 'rebuild' implies a full rewrite, which is a reasonable inference.

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 sentences, front-loaded with the main action, then the cost (download size and time), then usage guidance. No redundant information; every clause earns its place.

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 zero-parameter, no-output schema tool, the description adequately covers what it does, the resources involved, and when to use it. There is no missing critical information needed for an agent to decide to invoke it.

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 tool has zero parameters, so the schema already provides complete coverage. The description adds contextual meaning about the operation's scale and purpose, which is sufficient given there are no parameters to explain.

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 downloads and rebuilds the local component catalog from a specific snapshot source, distinguishing it from sibling tools that handle queries or orders. It uses specific verbs ('download and rebuild') and specifies the resource affected.

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 explicitly says to use 'occasionally' to pick up new components and clarifies that live stock/pricing is always current regardless, implying this refresh is not needed for those queries. This provides clear guidance on when to use the tool without naming alternatives.

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