szlcsc_download_parts

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

The description does not disclose any behavioral traits beyond the name, such as the fact that it may overwrite files (force parameter) or that it downloads from a specific source. There are no annotations to provide safety hints, so the description carries the full burden but fails to mention important behaviors like overwriting behavior or network usage.

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 extremely concise, being a single sentence. It is well-structured and front-loaded with the action. However, it might be too brief, as it omits crucial details, but for the information it conveys, it is efficient.

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 complexity (batch operation, multiple parameters, no annotations, no output schema details except its existence), the description is insufficient. It does not explain the return format, error handling, or how it relates to other download tools, leaving major gaps for an agent to use it correctly.

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%, and the description does not explain the purpose of each parameter beyond the schema. 'identifiers' could be ambiguous (are they part numbers or IDs?), 'output_root' implies a directory but no format, and 'force' is not clarified beyond its default. The description should compensate for the lack of schema coverage but does not.

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 states a specific action: batch download and organize complete documentation directories for multiple components. It distinguishes from sibling tools like szlcsc_download_part (singular) and szlcsc_sync_datasheets (syncing), but it lacks explicit mention of output behavior, which could clarify its role further.

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 alternatives. For example, it doesn't explain whether it can be used for single components or if szlcsc_download_part should be used for single units, nor does it mention any prerequisites like prior searching.

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