pcb_get_net_primitives

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

描述仅说'查询'，暗示只读操作，但未明确声明无副作用、无需权限或返回内容的结构，也没有提及可能的行为限制。鉴于无注释，描述承担全部责任，但信息不足。

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?

描述为单一简短句子，无冗余信息，信息密度高，易于快速理解。

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?

工具结构简单（单参数、无输出模式），但描述未说明返回的数据结构或可能包含的图元类型，在无输出模式的情况下，代理可能对返回值有不确定性，但整体信息足以基本理解功能。

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?

参数'net'在输入模式中已描述为'网络名称'，模式覆盖率为100%，描述未添加额外语义。根据规则，高覆盖率下基准为3。

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?

描述明确说明'查询指定网络的所有图元'，动词'查询'和资源'所有图元'清晰表达了操作对象，与获取轨道、焊盘等特定类型工具存在区别，但未明确说明与其他获取工具的具体差异。

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?

没有提供何时使用此工具而非其他类似工具（如pcb_get_tracks、pcb_get_pads）的指导，没有提及替代方案或使用场景。

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