eda_pcb_drc_overwrite_region_rules

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

With no annotations, the description carries the full burden. It explicitly warns '将会覆写当前 PCB 的所有区域规则，请注意数据丢失风险' (will overwrite all region rules, risk of data loss), disclosing the destructive, irreversible nature. It also specifies returns a boolean indicating success. However, it does not elaborate on how the overwrite affects existing rules not provided in the input array, which is a notable gap.

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, containing a signature line, a brief Chinese purpose, a warning remark, and a return note. Each part contributes essential information. It could be slightly more structured (e.g., separating prerequisites and parameter explanation), but it remains efficient and front-loaded.

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?

The tool is a mutation with no annotations, no output schema, and a complex parameter (array of Record). The description lacks details on the structure of regionRules, required vs optional fields, and how to construct valid records. It also omits any mention of prerequisites like an active PCB document. This leaves an agent under-equipped to correctly invoke the tool.

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?

Schema coverage is 100% for top-level parameters (args and windowId), so baseline is 3. The description adds the function signature with 'regionRules: Array<Record<string, any>>', giving type information but no details about required fields or structure of each record. This is more than the generic args description provides but still insufficient for a complex array parameter.

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 tool overwrites region rules via the Chinese '覆写区域规则' and the explicit remark '将会覆写当前 PCB 的所有区域规则' (overwrites all region rules of the current PCB). It identifies the specific resource (region rules) and scope (all of current PCB), distinguishing it from net-rule or configuration overwrites, though it does not explicitly compare with sibling 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?

The description provides no guidance on when to use this tool versus alternatives like eda_pcb_drc_overwrite_net_rules or eda_pcb_drc_get_region_rules. It does not mention prerequisites (e.g., PCB open) or scenarios where this is appropriate. The only guidance is the implied 'overwrites all' warning, which is behavioral rather than usage-directed.

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