sch_get_netlist

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

With no annotations, the description carries the full burden for behavioral disclosure, but it only says 'export netlist.' It does not state whether the tool returns the netlist content, writes a file, has side effects, or requires an open schematic, leaving important behavior undocumented.

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 has no filler and is front-loaded, but it is a single terse phrase with no elaboration. It is under-specified rather than appropriately concise, similar to a placeholder-level description.

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 no annotations, no output schema, and an optional format parameter, the description leaves critical context missing: valid values for 'type', default behavior, return format, and whether any schematic state is required. An agent would have to guess or call the tool blindly.

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's description of 'type' as '网表格式' (netlist format) gives basic meaning to the only parameter, and schema coverage is 100%, so the baseline is 3. The tool description adds no extra parameter guidance, such as accepted format values or what happens when the optional parameter is omitted.

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 and object: '导出网表' (export netlist), which clearly identifies the tool's function. It does not explicitly distinguish itself from sibling tools, but no sibling performs netlist export, so the purpose is unambiguous.

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 alternatives, no prerequisites, and no mention of whether it should be run after schematic editing or before PCB layout. The agent must infer usage entirely from the tool name and terse description.

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