pcb_create_copper_pour

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

没有 annotations，描述需承担全部行为披露责任，但它只说“创建”，未提及对已有铺铜区域的影响、层或网络有效性、调用后如何确认结果等。对于写操作而言，行为透明性不足。

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?

参数 schema 完整且无嵌套对象，复杂度较低；但无 annotations 和 output schema，描述也没有提供调用时机、与兄弟工具的区分或结果返回方式。基本可完成调用，但缺少边界场景和备选工具信息。

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?

input schema 对所有 6 个参数均有描述，覆盖率 100%，因此描述无需重复参数含义。描述中的“矩形”仅与 x1/y1/x2/y2 的几何意义泛泛对应，未额外增加参数格式、单位或约束信息。

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?

描述仅陈述功能，未说明何时应选择铺铜而非走线、keepout 或其他创建类工具。没有列出替代工具或排除条件，代理只能从工具名和上下文推断使用时机。

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