sch_get_netlist

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

With no annotations provided, the description carries the full burden. It only states 'Export netlist' with no mention of side effects, expected output, permissions, or whether it writes a file or returns data. Completely silent on behavior beyond the action.

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 a single short phrase, which is concise, but it is under-specified. It does not front-load any useful information beyond the tool name's meaning; it is more of a tautology than a helpful summary.

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 simple tool with one parameter and no output schema, the description is still inadequate. It omits critical details like supported formats, how the netlist is delivered, and integration with other schematic tools. The tool could be better specified with a sentence about output behavior.

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 100% description coverage for the single 'type' parameter, so the baseline is 3. The description adds no additional parameter context, but the schema already explains '网表格式' (netlist format).

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 '导出网表' (Export netlist) provides a verb and resource, but lacks specificity about what kind of netlist, format, or context. It is distinguishable from siblings like sch_generate_from_netlist but not clearly differentiated in scope.

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 such as pcb_netlist_report or sch_generate_from_netlist. No context or prerequisites are mentioned.

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