eda_pcb_manufacture_data_get_bom_templates

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

With no annotations, the description carries the full burden. It discloses the return shape via 'Promise<Array<string>>' and 'returns: BOM 模板列表', which is useful. However, it does not explicitly state that the operation is read-only or describe any scope or side-effect behavior beyond the get action.

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 short, but it is somewhat redundant: '获取 BOM 模板列表' and 'returns: BOM 模板列表' say nearly the same thing. The signature line is informative, but the duplicated return information wastes some space.

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 list retrieval, the description is mostly sufficient: it states the return type and content. Yet it lacks context about related sibling operations or any prerequisites, and with no output schema a bit more explanation of the returned template list would improve completeness.

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 coverage is 100%, so the schema already documents the args and windowId parameters. The description adds no parameter-level meaning, so the baseline of 3 applies rather than a lower score.

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 '获取 BOM 模板列表' (get BOM template list), giving a clear verb and resource. The signature also indicates a retrieval operation returning an array of strings. It is distinguished from the sibling get_bom_template_file by emphasizing the list rather than a single file.

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 such as get_bom_template_file, upload_bom_template_file, or delete_bom_template. The intended usage is implied only by the name and 'get list' wording.

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