eda_pcb_net_unhighlight_net

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

With no annotations, the description carries the full burden. It explicitly discloses that the return is result-oriented and returns true even if the net was not previously highlighted, which is a valuable non-obvious behavioral detail. It does not mention other potential side effects, but for a simple unhighlight operation this is sufficient.

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 concise and front-loaded with the signature, followed by the action in Chinese, a remark, and the return type. It is efficient and without wasted words, though the mixed-language format could be more unified.

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 net unhighlight operation, the description covers the return value and the idempotent behavior. The windowId parameter is documented in the schema, so no further explanation is needed. Minor gaps like case sensitivity of net names are not critical.

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 describes args as a generic JSON array, but the description's signature 'pcb_Net.unhighlightNet(net: string)' clarifies that the first parameter is the net name string. This adds meaning beyond the schema, which is crucial for correct invocation.

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 clearly states the action '取消高亮网络' (cancel highlight net) and provides the method signature pcb_Net.unhighlightNet(net: string). This distinguishes it from siblings like eda_pcb_net_highlight_net and eda_pcb_net_unhighlight_all_nets by targeting a single net.

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?

The description does not provide any guidance on when to use this tool versus alternatives such as unhighlight_all_nets or highlight_net. It lacks exclusions or conditions, leaving the agent to infer usage from the name alone.

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