add_wires

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

Annotations indicate readOnlyHint=false (mutating) and destructiveHint=false (non-destructive). The description confirms an additive operation. No additional behavioral details (e.g., side effects, permissions, error conditions) are provided beyond 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?

The description is three sentences: first states purpose, second details wire dict keys, third lists args. It is front-loaded and concise with no redundant information.

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?

Given the tool has only two parameters, the description is mostly complete. It explains both params and the operation. Minor gaps exist (e.g., coordinate range constraints), but with an output schema present, return values are not required. Overall adequate for a simple additive tool.

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 input schema has 0% description coverage, so the description carries full burden. It clearly explains the 'wires' parameter as a list of dicts with keys x1, y1, x2, y2, and defines schematic_path as 'Path to .kicad_sch file'. This adds significant meaning beyond the schema's minimal structural definition.

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 tool's purpose: 'Add multiple wires at once' and specifies the structure of each wire dict. It distinguishes itself from sibling tools like add_traces (PCB) and add_symbols by focusing on wires and using schematic_path.

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 description implies usage for adding wires to a KiCad schematic via schematic_path, but does not explicitly mention when to use this tool over alternatives like add_traces or remove_wire. No exclusions or alternative tool references are provided.

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