detect_pin_conflicts

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

No annotations are provided, so the description carries the full burden. It clearly lists the four types of checks performed (multiple outputs, power-to-power, unconnected inputs, pin type mismatches), which gives insight into the tool's behavior. However, it does not explicitly state whether the tool is read-only or if it modifies the schematic, though 'detect' implies no side effects.

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 concise: a one-line summary followed by a focused bullet list. It is front-loaded with the main purpose, and every sentence adds value. No redundant or unnecessary 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 an output schema (context signals indicate true), the description does not need to explain return values. It adequately covers what the tool checks. Could potentially mention prerequisites or scope, but it is sufficient for understanding the tool's purpose in the context of sibling analysis tools.

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 one parameter with 100% description coverage ('Path to .kicad_sch file'). The tool description does not add any additional meaning beyond the schema, so it meets the baseline for high schema coverage.

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 function: 'Detect pins with conflicting electrical connections' and lists specific conflict types (multiple outputs, power-to-power, unconnected inputs, pin type mismatches). This distinguishes it from sibling tools like analyze_pin_functions or validate_pin_configuration by focusing on electrical conflicts rather than general analysis.

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 does not explicitly state when to use this tool versus alternatives. While the list of checks implies usage scenarios (e.g., debugging wiring issues), there is no guidance on when not to use it or mention of related tools. Siblings like analyze_pin_functions or trace_netlist_connection could overlap, but no differentiation is provided.

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