pcb_manage_diff_pairs

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

Annotations already declare destructiveHint=true, idempotentHint=false and openWorldHint=false, so the safety profile is covered. The description adds the per-action breakdown but does not disclose that delete/rename are irreversible, whether modify_nets disrupts existing routing, or any confirmation/auth requirement — modest value on top of 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?

Purpose is front-loaded in one sentence, followed by a tight bulleted action list. Every line carries information and there is no padding, though the format is a fairly standard enumeration.

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 multi-action tool with no output schema, the description covers the action set and parameter mapping well. It omits what get_all returns and any error/failure semantics, but the schema carries the document/instance_id requirements, leaving only a minor gap.

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%, so the baseline is 3, but the description goes further by mapping parameters to the specific action that consumes them (create→name/positiveNet/negativeNet, rename→originalName/newName, etc.), which the flat schema does not express. This mapping is genuine added meaning.

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+resource ('Manage differential pair definitions') and enumerates all five actions with their target fields, so an agent knows exactly what this tool covers. The resource (differential pairs) is distinct from siblings like pcb_manage_net_classes or pcb_manage_equal_length_groups.

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 mode applies, but there is no explicit guidance on when to choose this tool over the other pcb_manage_* tools, nor any prerequisites (e.g. that nets must already exist). Usage is inferable but not stated.

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