export_bom

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

With no annotations, the description carries the full burden of behavioral disclosure. It does not mention potential side effects (e.g., file creation/overwriting), whether the schematic must be open, or any permissions required. The phrase 'Export ... to CSV' implies writing but is not explicit.

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, front-loaded sentence directly states the tool's operation without wasteful words.

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 minimal 2-parameter schema and no output schema, the description gives the core action but omits details like default output path, whether the tool writes files, and error conditions. It is adequate but incomplete for an agent needing to invoke it safely.

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 descriptions are 0% covered. The description partially compensates by linking 'schematic' to the required path parameter and 'CSV' to the output parameter, but it doesn't explain the optional output behavior or default.

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 names an explicit verb 'Export' and identifies the resource 'a Bill of Materials from a schematic' and the format 'CSV via kicad-cli', making it clear and distinct from sibling tools like export_schematic.

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 instead of alternatives, nor any prerequisites or exclusions. The description only states the action, leaving users to infer usage context.

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