Export Sch Pdf

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

Annotations already declare destructiveHint=true, so the description need not repeat that. It adds useful context about using kicad-cli and the set of options, but does not explain what destructive means (e.g., overwriting output) or other side effects. This is acceptable given annotation coverage but not exceptional.

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, front-loaded sentence starting with the core purpose. The parenthetical option list is long but compact and scannable, though it partly duplicates schema information. No unnecessary 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?

For a complex 13-parameter tool with an output schema, the description covers the main function and option set but omits critical contextual details like overwriting behavior and the fact that outputPath is also required. It is minimally viable but leaves gaps.

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 100%, so parameters are already well documented. The description broadly enumerates many option names but adds little meaning beyond the schema, only highlighting schematicPath as required. Baseline 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 tool's function: 'Export a schematic to PDF via kicad-cli (`sch export pdf`)'. It provides a specific verb, resource, and underlying command, and distinguishes itself from sibling tools by focusing on schematic PDF export with the full option set.

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 when-to-use guidance is provided. The description does not compare this tool to siblings like export_pdf or export_schematic_pdf, nor does it state conditions for choosing it over alternatives. The only usage hint is that schematicPath is required, which is already in the schema.

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