kicad_ctrl_netlist_diff

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 describes the output (diff of nets and components) and the practical implication (which traces need rerouting). It does not discuss potential side effects, required permissions, or error handling, which would be needed for a higher score.

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 efficient sentences plus an imperative instruction. Every sentence adds value: function, output, practical reason, and important note. No fluff.

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 diff tool with good param descriptions and an output schema, the description covers the core functionality, practical use case, and a key warning. It leaves no significant gaps for typical usage.

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?

Input schema coverage is 100% with clear parameter descriptions. The description adds value by explaining that 'old_schematic' defaults to git if not provided, and by setting context that 'project_path' is the new schematic. This goes beyond the schema alone.

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 verb 'compare' and the resource 'old and new schematic netlists', and explains the output (added/removed/modified nets/components). It distinguishes from siblings like kicad_ctrl_analyze or kicad_ctrl_erc, which serve different purposes.

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 usage context: 'Review the diff before proceeding to PCB analysis.' It implies the tool is for pre-PCB tasks. However, it does not explicitly mention when not to use it or name alternative tools for exclusion.

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