Export Sch Svg

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

The annotations indicate destructiveHint=true, but the description does not explain what destructive behavior occurs (e.g., overwriting files, creating directories). It adds only basic context about writing one SVG per page into a directory, but fails to disclose the full side effects or permission needs.

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 and front-loaded with the main purpose, followed by a compact list of options. The only slight issue is the incomplete required-note sentence, making it not perfectly accurate but still overall 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?

The description covers core behavior (export to SVG, one per page, supported options) and benefits from an existing output schema. However, it does not clarify output directory handling, potential overwrite behavior, or address the destructive annotation, leaving gaps for an agent invoking the tool.

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 already provides 100% field descriptions, so the baseline is 3. The description adds minimal value by listing option names but also misleadingly highlights 'schematicPath is REQUIRED' while omitting that outputDir is also required, potentially causing confusion about required parameters.

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 exports a schematic to SVG via kicad-cli, with specific behavior (one SVG per page into a directory). It distinguishes from siblings like export_sch_pdf by specifying the SVG format and CLI-based approach.

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 implies usage for CLI-based SVG export and lists available options, but it does not explicitly state when to use this tool over alternatives like export_sch_pdf or export_schematic_svg, nor does it mention exclusions or prerequisites beyond the required parameter.

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