eda_pcb_manufacture_data_get3_dfile

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

No annotations exist, so the description bears full responsibility for behavioral disclosure. It reveals the return type (Promise<File | undefined>) but does not explain side effects, whether files are downloaded or generated, what 'autoGenerateModels' implies, or how the windowId/active-window behavior affects the operation.

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 front-loaded with the signature, followed by a one-line Chinese summary and return note. It wastes little space, though the summary and return line are somewhat redundant with each other.

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 tool with five optional parameters, no output schema, and many sibling manufacture-data getters, the description is incomplete. It lacks parameter explanations, when-to-use guidance, output format details, and any clarification of the relationship to the get3_dshell_file sibling.

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 exposes an opaque args array and windowId, so the function signature in the description is the primary source of parameter meaning. It lists each parameter name, type, optionality, enum literals, and official order, which is valuable. It does not deeply explain each option's semantics, but the names and enum values are mostly self-explanatory.

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 ('获取 3D 模型文件' / get 3D model file) on a specific resource, and the included function signature adds details like file type and element selection. However, it does not distinguish this from the nearby sibling eda_pcb_manufacture_data_get3_dshell_file, leaving some ambiguity about which 3D-related file tool to choose.

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 about when to use this tool versus other manufacture-data getters, such as get3_dshell_file, get_dxf_file, or get_gerber_file. No context, prerequisites, or exclusions are provided, so the agent must infer usage solely from the tool name and signature.

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