eda_sys_tool_netlist_comparison

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

Annotations are absent, so the description carries the full burden of behavioral disclosure, but it only provides a function signature and a short return label. It does not state whether the operation is read-only, what side effects occur, how errors are handled, or what role the active window/windowId plays. The return type is exposed but its meaning is not elaborated, leaving a significant transparency gap.

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 type signature, containing no filler prose. The final 'returns: 网表对比结果' is somewhat redundant with the arrow return type, but the overall length is minimal and every other element carries information. It could be more human-readable, but it is appropriately terse.

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 an effectively empty generic schema, no annotations, and no output schema, the description needed to explain how to supply netlists and how to interpret the returned differences. It offers only type signatures and a Chinese label, leaving the agent without guidance on input formats, output semantics, or windowId usage. This is insufficient for a two-input comparison tool.

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 signature adds real parameter structure beyond the generic `args` array with empty `items {}`, namely the union types for netlist1/netlist2 and the output element shape. However, it does not explain what a string netlist represents (raw content, path, or reference), what the File type refers to, or how projectUuid/documentUuid identify sources. Thus the description partially compensates for the sparse schema but leaves key semantics ambiguous.

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 function name and the Chinese label '网表对比' (netlist comparison) plus the typed signature make the purpose inferable: comparing two netlists and returning per-object name differences. It is distinguishable from sibling pcb/schematic comparison tools by the netlist resource. However, it never fully states in plain language that it compares two netlists and reports differences, relying instead on the name and terse label.

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 versus eda_sys_tool_schematic_comparison, eda_sys_tool_pcb_comparison, or the netlist getter tools like eda_sch_netlist_get_netlist. No selection conditions, prerequisites, or exclusions are mentioned. An agent must infer usage solely from the tool name.

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