szlcsc_library_sync

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

With no annotations, the description carries full burden and discloses key behaviors: it refreshes metadata, does *not* rebuild CAD, and flags MPN/package changes for review. It lacks details on authentication, rate limits, or error handling, but the core behavioral traits are well covered.

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 that front-load the main action and follow with critical caveats. It is efficient with no word waste, though a bulleted or more structured format could improve scannability for the agent.

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 covers the core operation and important behavioral nuances (no CAD rebuild, flagging). However, it fails to explain parameters or output schema (though output schema exists, its content is unknown), and omits usage boundaries relative to similar siblings, leaving the agent with incomplete context.

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%—no parameter descriptions exist. The tool description does not explain any of the three parameters (dedupe_cad, identifiers, library_root). While parameter names offer some hint, the description adds no semantic value beyond the bare names.

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 refreshes library metadata (price, stock, datasheets) and explicitly notes it does not rebuild CAD. However, it does not distinguish this sync operation from sibling tools like szlcsc_library_search or szlcsc_library_add, leaving the agent to infer the difference.

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?

No guidance is provided on when to use this tool versus its many siblings (e.g., szlcsc_library_audit, szlcsc_library_merge). The description implies it is for refreshing existing library entries, but the agent receives no explicit when-not or alternative suggestions.

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