pcb_manage_equal_length_groups

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

Annotations already declare destructiveHint=true, readOnlyHint=false and idempotentHint=false, so the safety profile is covered structurally. The description adds no behavioral context beyond restating action names — it never says what delete destroys (whether nets are removed from the board), whether changes persist, or what a destructive call requires.

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?

A single front-loaded purpose sentence followed by a compact bulleted action list; every line earns its place with no filler or repetition.

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?

Covers all six actions and their parameter routing, which is adequate for a multi-action tool. But with no output schema and nine parameters, the description never indicates what get_all returns or what success/error responses look like, leaving a real gap for the read action.

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 description coverage is 100% and every parameter already carries a '(for X)' usage note, so the schema does the heavy lifting. The description's per-action parameter mapping largely duplicates that, adding little new meaning; baseline 3 is appropriate.

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?

States a specific verb and resource ('Manage equal-length net groups') and enumerates six concrete actions, so the agent knows exactly what domain it operates on and can distinguish it from siblings like pcb_manage_net_classes or pcb_manage_diff_pairs. It stops short of explicitly contrasting itself with those siblings, so it is clear but not fully differentiated.

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 action list implies when each sub-operation applies, and the parenthetical parameter hints (e.g. 'create group (name, nets: string[]; color optional)') give some operational guidance. However there is no explicit when-to-use/when-not-to-use guidance and no routing to alternative tools for related concepts such as net classes or pad-pair groups.

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