export_schematic

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

With no annotations, the description carries full burden. It states the output formats and mentions kicad-cli, but does not disclose that the tool writes a file to disk, whether it overwrites existing files, or any required permissions or side effects. This is minimal behavioral transparency for a tool with no annotation support.

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 that is front-loaded with the action and resource, and every word adds value. It is appropriately sized for a simple tool with a clear purpose, avoiding unnecessary detail.

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 absence of annotations and an output schema, the description should provide more context about invocation, expected results, and limitations. It only covers the 'what' and not the 'how' or 'when', leaving significant gaps for correct 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?

Schema description coverage is 0%, so the description must compensate. It implicitly covers the 'fmt' parameter by listing allowed formats, but it offers no explanation for the required 'path' parameter or the optional 'output' parameter. The meaning of these parameters is left entirely to the schema, which lacks descriptions.

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 uses a specific verb 'plot' with a clear resource 'schematic' and enumerates the supported output formats (pdf, svg, dxf, ps, hpgl). This clearly distinguishes it from sibling tools like export_bom or schematic_netlist, which focus on other output types.

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 guidance is provided on when to use this tool versus alternatives. It does not mention that for netlist export one should use schematic_netlist or for BOM export use export_bom. The only contextual hint is 'via kicad-cli', but that does not clarify selection criteria.

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