eda_pcb_drc_delete_pad_pair_group

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

With no annotations, the description carries the full burden of behavioral disclosure, but it only reveals the return type (Promise<boolean>) and success semantics. It does not state that deletion is permanent, what happens to pad pairs inside the group, or any error conditions, which is a significant gap for a destructive operation.

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 three short lines—signature, Chinese meaning, and return semantics—with no filler or redundancy. It is front-loaded and every element earns its place.

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 simple one-parameter delete operation, the signature, parameter type, and return value provide a viable minimum. However, it omits important context such as how to obtain a valid padPairGroupName, whether deletion is reversible, and side effects on contained pad pairs; with no output schema or annotations, this is adequate but not complete.

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 schema's args items are generic/empty, but the description's signature adds the actual parameter name and type (padPairGroupName: string), meaningfully supplementing the generic 'JSON parameter array' description. The top-level windowId and args order are already documented in the schema, so the addition is targeted and useful.

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 operation via the function signature pcb_Drc.deletePadPairGroup and the Chinese '删除焊盘对组' ('delete pad pair group'), identifying both the action and the resource. It does not explicitly differentiate from sibling DRC delete tools, but the target resource is unambiguous.

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?

There is no when-to-use or alternative guidance. The description only restates the operation itself and never mentions prerequisites, such as the group needing to exist, or how to discover valid group names via sibling tools like eda_pcb_drc_get_all_pad_pair_groups.

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