sch_add_wire

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

The description adds the useful behavioral detail that endpoints snap to a 2.54 mm grid by default, which goes beyond the destructiveHint annotation. However, it does not elaborate on what modifications occur or whether the operation can be undone, though the annotation already indicates destructive intent.

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 a single concise sentence that immediately conveys the core function and a key default behavior. No unnecessary words 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?

For a relatively simple wire-addition tool, the description gives the essential action and default snapping behavior. However, it lacks usage context, does not mention any limitations or interactions with existing wires, and only minimally connects to the schema parameters, leaving some gaps for an AI agent.

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?

With 0% schema coverage, the description must compensate for the undefined parameters. It implicitly references endpoints and the snap_to_grid parameter via 'snapping... by default', but it does not explain the coordinate parameters (x1_mm, y1_mm, etc.) or their units beyond what the parameter names suggest.

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 adds a schematic wire, with a specific verb and resource. It also notes the default grid snapping behavior, which helps distinguish it from related tools like sch_route_wire_between_pins, though it does not explicitly name alternatives.

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 provides no guidance on when to use this tool versus alternatives such as sch_route_wire_between_pins or sch_add_bus. There is no mention of prerequisites, preferred scenarios, or exclusions.

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