Export Position File

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

Annotations already indicate destructiveHint=true, so the agent knows writes can be destructive. The description adds that it uses kicad-cli and is a compact alias, but doesn't elaborate on potential side effects like overwriting existing outputPath files. This adds minimal behavior beyond the annotations.

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 two sentences, front-loads the purpose, and clearly states the tool's scope. No 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?

Given the simple export function, full schema coverage, and presence of an output schema, the description is adequate. It identifies the tool's purpose, the fact it's a compact alias, and the core exposed options. Could benefit from an explicit note on file overwriting behavior, but annotations partially compensate.

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 fully describes all five parameters with 100% coverage, including enums and defaults. The description only mentions side, format, and units, which are already clear from the schema; it doesn't add additional meaning or relationships beyond what the schema provides.

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 function—'Export a component placement/position file through kicad-cli'—and differentiates from the sibling export_pos by characterizing it as a 'compact alias' exposing common options. This makes the tool's purpose unambiguous and distinguishes it from other export tools.

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?

It provides context for when to use this tool by noting it's a compact alias of export_pos, highlighting the common side, format, and unit options. However, it doesn't explicitly state exclusions or when to prefer the full export_pos, leaving some inference to the agent.

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