Kicad Pcb Assign Net

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

With no annotations, the description carries the full behavioral burden. It signals mutation and one special value, but says nothing about persistence (file written to disk?), permissions, error cases, or what happens to existing net assignments on rename.

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?

One front-loaded sentence with zero waste. However, terseness here is partly under-specification rather than true economy.

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?

An output schema exists, so return values need no explanation, but a mutating three-required-parameter tool with no annotations and 0% schema coverage needs far more than a single clause to be callable correctly.

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 all three parameters are required, yet the description explains none of them. Only 'net_number' gets partial meaning via the net-0 note; 'path' and 'net_name' format/constraints are left entirely to inference.

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?

Specific verb pair ('declare or rename') plus resource ('a net in the PCB netlist'), with a useful scope note about net 0. No sibling is a close substitute, so the lack of explicit differentiation costs little.

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 on when to use this versus adding tracks/footprints that imply nets, nor any prerequisite (must the board be open, does the path point to a .kicad_pcb?). The net-0 note is a usage hint but not routing guidance.

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