pcb_create_copper_pour

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?

输入模式覆盖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?

描述明确说明创建矩形铺铜区域，动词和资源具体，但未与兄弟工具（如pcb_create_keepout）区分。

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?

没有提供何时使用该工具与替代方案的指导，缺乏使用场景描述。

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