eda_sch_manufacture_data_get_png_file

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

With no annotations provided, the description carries the full burden of disclosing behavior. It explains the maximum resolution of 4096, the optional width/height behavior, the default 1x output when both are omitted, and the return type Promise<File | undefined> plus the possibility of a compressed package. This is substantial, though it does not mention prerequisites or side effects.

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 logically organized: signature, one-line purpose, bullet-style remarks, version availability, and return information. Every line contributes useful information, though the formatting is a bit dense for an agent to parse quickly.

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 an export tool with no output schema and no annotations, the description covers the return value, resolution limits, default behavior, and availability version. It does not explain how fileName is used or the exact shape of ISCH_ExportPngResolution, but overall it is reasonably complete for its complexity.

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 input schema only contains a generic args array and windowId, so the description supplies the real parameter semantics: fileName?: string and resolution?: ISCH_ExportPngResolution, including the scaling rules for width/height. This adds meaning well beyond the generic schema definition.

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 action '获取 PNG 文件' and includes the method signature sch_ManufactureData.getPngFile, identifying the resource as a PNG export from schematic manufacture data. It is specific about the verb and resource, but it does not explicitly distinguish itself from sibling export tools such as get_svg_file or get_pdf_file, so it stops short of a 5.

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 instead of alternatives like SVG, PDF, or BOM export tools. The remarks explain parameter behavior but do not state when PNG export is appropriate or when another sibling tool should be chosen.

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