pcb_bind_pad_nets

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

With no annotations, the description carries the full burden and does well: it discloses the non-creating failure mode for missing nets, the ordering/caching constraint on adjacent designators, and the aggregate bound/failed plus capped missing_* lists. It stops short of saying what happens to a pad that already carries a different net (overwrite vs. error) and says nothing about permissions or undo, which is the one real gap for a mutation tool.

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 critical constraint (nets must pre-exist) is front-loaded and each paragraph adds new information. Minor waste: the "Returns:" block largely restates the existing output schema, and the "Second leg of the netlist-driven SCH->PCB bridge" framing is atmospheric rather than operational.

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 single-parameter batch tool with an output schema, this covers everything an agent needs: prerequisite tool, input row shape, ordering requirement, failure semantics, and result shape. Nothing material is left to inference.

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 0% and the schema only says "array of objects with additionalProperties: true", so the description must compensate — and it does, spelling out the three required keys `designator` ("U1"), `pin` (pad name, "3" or "A1"), and `net`, with concrete examples.

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?

Starts with a specific verb+resource+scope: "Assign component pads to existing board nets, batch in ONE call." It also positions itself against the sibling `pcb_create_nets_from_list` as the second leg of the same bridge, so an agent can place it precisely in the workflow without opening a schema.

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?

Explicitly states the prerequisite ("after `pcb_create_nets_from_list`"), the correct input source (every (designator, pin, net) row of the compiled netlist), and a hard exclusion: nets must already exist, a binding to a missing net fails and does not create it. It even names `pcb_build_from_project` as the sibling that produces correctly ordered rows.

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