wire_pins_to_net

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

Describes 'Single file load/save cycle', adding behavioral context beyond annotations. Annotations show non-read-only, non-destructive, non-idempotent, which aligns. No contradiction.

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?

Concise, front-loaded with purpose, then batch note, then parameter list. Slightly redundant mention of 'Batch version' but overall efficient.

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?

Covers usage well for a tool with 6 parameters and output schema. Does not describe return value, but output schema likely handles that. Adequate given complexity.

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 description coverage, the description fully explains each parameter: pins as list of dicts, label_text, direction with options, stub_length default, auto_pwr_flag, schematic_path. This adds significant value.

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?

Clearly states the verb 'wire' and the resource 'multiple component pins to the same net label'. Distinguishes from sibling tools like connect_pins and add_label by specifying it's a batch version of wire_pin_to_label.

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?

Indicates it's a batch version of wire_pin_to_label, implying use when wiring multiple pins to one net. Does not explicitly state when not to use, but the context is clear.

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