Export Schematic Pdf

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

Annotations already indicate destructiveHint=true, so the description need not repeat that. However, it adds minimal behavioral context beyond mentioning 'using kicad-cli', which hints at external tool dependency. It does not disclose that exporting may overwrite the output file or that kicad-cli must be installed.

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?

A single, concise sentence that front-loads the essential action and format. No wasted words or redundant information.

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 is adequate for a simple export tool, and the schema/annotations cover the key details. However, it omits behavioral specifics like file overwriting behavior and doesn't clarify the relationship to similar export tools, leaving some contextual gaps for an agent.

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%, and the schema itself provides clear parameter descriptions (e.g., output path, blackAndWhite flag, schematic file path). The description adds no extra parameter-level meaning, 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 (Export), resource (schematic), and output format (PDF), making the primary purpose obvious. However, it does not distinguish this tool from the similarly named sibling 'export_sch_pdf', which likely serves the same function.

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 vs. alternatives like export_sch_pdf or export_pdf. The description simply states the function without contextualizing its use among the many export-related siblings.

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