eda_sch_manufacture_data_get_svg_file

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

No annotations are provided, so the description must carry the behavioral disclosure burden. It does add useful behavioral detail: the return type `Promise<File | undefined>`, the remark that multi-page schematics export as a ZIP archive, and the EDA version availability. It does not mention prerequisites, side effects, or what happens when `fileName` is omitted, so coverage is adequate but incomplete.

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 compact and well structured: signature, one-line purpose, one key behavioral remark, version note, and return summary. There is little waste, though the bilingual repetition and version note are marginally unnecessary for invocation.

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?

With no annotations and no output schema, the description covers the important return-shape details including the multi-page ZIP edge case. However, it omits usage context, `fileName` semantics, and which document or page is exported, leaving some ambiguity for an agent deciding how to call 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 schema only provides a generic `args` array and `windowId`, so it does not document the actual function parameter. The description's signature adds `fileName?: string`, which reveals the name, type, and optionality, but it never explains what `fileName` represents or how it interacts with the current document. This is a modest improvement over the schema, not full parameter semantics.

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 opens with the exact API signature `sch_ManufactureData.getSvgFile(fileName?: string)` and the clear purpose '获取 SVG 文件' (get SVG file), stating a specific verb and resource. The SVG file-type target also differentiates it from sibling export tools such as `eda_sch_manufacture_data_get_png_file` and `eda_sch_manufacture_data_get_pdf_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?

The description gives no explicit when-to-use or when-not-to-use guidance, and names no alternatives. An agent can infer this tool is for obtaining an SVG file from the schematic manufacture-data group, but the usage context is implied rather than stated.

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