add_wire

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

With no annotations, the description carries the full burden. It explains routing behavior (L-corners, horizontal_first parameter), via insertion for layer changes, and unit (um). Does not mention destructive effects, but as a creation tool, this is expected.

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?

Three sentences, no fluff, front-loaded with core purpose. Every sentence adds value: wire type, routing algorithm, parameter meaning, and via guidance.

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 output schema exists, description need not cover return values. Covers essential aspects: wire geometry, parameters, and layer change hint. Missing constraints (min width, layer limits) are likely in schema.

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%, so description is crucial. It explains points (routes through points), horizontal_first (corner direction), and hints at via usage. Layer and width are not detailed, but their meaning is intuitive for a wire tool. Adds significant value beyond the schema.

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 'Manhattan wire' with axis-aligned segments, distinguishing it from siblings like add_path (arbitrary polylines) and add_box (rectangle). The verb 'add' and resource 'wire' are specific.

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?

Implies usage for orthogonal routing ('Manhattan wire', 'axis-aligned'). Mentions that for layer changes, users should drop an add_via, guiding on when to use alternative tools. Does not explicitly compare with add_path, but context provides differentiation.

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