Export EasyEDA Pro BOM

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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=false, and idempotentHint=false, so safety is covered. The description adds nothing about the notable side effect of this tool: it produces a file (where it is written, whether an existing file is overwritten, or what happens on timeout). Given idempotentHint=false, an agent would benefit from knowing why repeated calls may behave differently.

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?

A single well-formed sentence with no filler, so it is concise and front-loaded. However, that brevity leaves the definition under-specified rather than efficient, since space that could carry parameter or output detail is unused.

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 four-parameter export tool with no output schema and no documented parameters, the description should say where the export goes and what the result contains. It answers neither, so an agent cannot predict the outcome of a call beyond 'a BOM happens.'

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%, so all four parameters (scope, format, fileName, timeoutMs) are undocumented in both schema and description. The description does not explain what 'auto' scope resolves to, the output format tradeoffs, or the fileName/timeout behavior, leaving the agent to guess from bare enums.

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?

States a specific verb ('Exports') plus resource ('BOM') and scopes it to the active EasyEDA Pro project. This clearly separates it from other exporters such as export_gerber, export_cpl, and export_netlist, though the description itself doesn't name those alternatives.

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?

There is no guidance on when to choose a BOM export over the other export tools, nor on prerequisites (e.g., whether a project must be open or a schematic generated first). The agent must infer usage entirely from the title.

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