eda_pcb_drc_get_region_rules

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

With no annotations provided, the description carries the behavioral burden. It discloses that the tool is an async getter returning a Promise of an array of records and that it targets the current PCB, which implies a read-only operation. However, it does not mention prerequisites like whether a PCB document must be active, what happens when none is open, or any error/empty-result 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?

The description is compact and front-loaded with the API signature, followed by a short Chinese purpose and return note. It is appropriately short, though the 'returns: -' formatting is slightly awkward and the English/Chinese mix could be cleaner.

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 tool with no annotations, no output schema, and many similar DRC sibling tools, the description is too thin. It explains what is returned but not how region rules relate to other rule types, how window selection works, what the result entries contain, or when this tool should be preferred.

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 provides generic 'args' and 'windowId', but the description includes the official signature 'pcb_Drc.getRegionRules()', which reveals that no positional arguments are expected and that the args array should be empty. This adds meaningful interpretation beyond the 100% schema coverage.

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 states a clear verb-resource pair: '获取区域规则' (get region rules) and explicitly scopes the result to '当前 PCB 的所有区域规则' (all region rules of the current PCB). It is readily distinguishable from the many DRC sibling tools by name and scope, though it does not explicitly name or contrast those siblings.

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?

No guidance is given about when to use this tool versus related DRC retrieval tools such as get_net_rules, get_all_rule_configurations, or get_current_rule_configuration. The agent must rely on the tool name and very short description, with no exclusions or explicit alternatives.

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