eda_sch_netlist_set_netlist

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states 'update netlist' but provides no detail about side effects, whether the operation is reversible, what happens if the netlist is invalid, or whether it requires an active document. The signature shows Promise<void> but no further consequences are described.

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 extremely short, but it lacks meaningful content. Conciseness is positive only when the text is efficient and still informative; here it is under-specified, leaving critical details missing. The signature and single phrase do not earn their place because they do not aid in correct 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?

As a mutation tool with no annotations and no output schema, the description should explain return behavior, failure cases, and prerequisite conditions. It does none of these. An agent cannot determine how to construct the args correctly or anticipate the effect, making the definition inadequate for safe use.

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 has a generic args array and windowId, with 100% description coverage but no parameter-specific descriptions. The function signature mentions 'type: ESYS_NetlistType | undefined' and 'netlist: string', but the description does not explain what values are valid for type, what format netlist should take, or how windowId affects behavior. The description adds only the parameter names without semantic value beyond the schema.

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 is essentially the raw function signature plus the phrase '更新网表' (update netlist). It identifies the verb and resource, but gives no explanation of what 'set netlist' accomplishes in the schematic context. It is barely more than the tool name itself and does not help distinguish it from siblings like eda_sch_netlist_get_netlist beyond the obvious get/set polarity.

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 use this tool, what prerequisites exist (e.g., an open schematic), or when to prefer an alternative. The description is silent on any conditions or exclusions, leaving the agent to guess.

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