extract_netlist_from_project

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

With no annotations, the description must disclose behavior. It only says 'Extract netlist information', which implies a read-only operation but does not confirm if the tool modifies the project or what 'netlist information' includes. The existence of an output schema mitigates some transparency, but the description adds no behavioral context.

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 extremely concise (6 words, 1 sentence). While it lacks structure, it wastes no words. It could benefit from brief context but is 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?

For a simple extraction tool with an output schema, the description is minimally adequate. However, it does not mention what the netlist information contains, how to interpret the output, or any constraints (e.g., file existence). The high context signal of an output schema reduces the burden, but the description still feels incomplete.

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 schema has 100% coverage and the only parameter (project_path) has a clear description in the schema. The tool description adds no additional meaning beyond what the schema already provides, so a baseline score of 3 is appropriate.

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 action ('Extract netlist information') and the target resource ('from a KiCad project'), distinguishing it from sibling tools like extract_bom_from_kicad. The verb 'extract' and resource 'netlist' are specific and unambiguous.

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 (e.g., extract_bom_from_kicad, kicad_ctrl_analyze). There are no notes on prerequisites (e.g., project must have a valid netlist) or limitations.

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