export_netlist

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

Annotations declare 'destructiveHint' and 'openWorldHint', but the description adds no context about what these mean in practice (e.g., whether it writes a file, overwrites existing files, or has side effects). The description simply restates the tool's function without disclosing behavioral traits beyond what the annotations already hint at.

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 a single sentence with no wasted words. It is appropriately sized for a simple tool, though it is very terse. It lacks any structured breakdown of parameters or behavior, but for pure conciseness it does not contain filler.

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?

With only one optional parameter and an output schema present, the tool is relatively simple. However, the description omits crucial context about the 'format' parameter and the distinction from 'export_spice_netlist'. The annotations provide some safety context, but the absence of parameter guidance and usage alternatives makes the description incomplete for reliable tool invocation.

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 description coverage is 0%, and the only parameter 'format' is not described in the tool description. The agent has no idea what valid formats are (beyond the default 'kicad') or what the parameter controls. The description provides no compensation for the missing schema information.

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 states a clear verb ('Export') and resource ('KiCad schematic netlist'), so the core purpose is clear. However, it does not distinguish itself from the sibling tool 'export_spice_netlist', which also exports a netlist. Without this differentiation, an agent may not know which to choose.

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?

No usage context is provided. There is no guidance on when to use this tool versus alternatives like 'export_spice_netlist', nor any prerequisites or expected inputs beyond the schema. The agent is left to infer usage solely from the name.

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