mfg_import_geda

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

The description adds no behavioral context beyond the openWorldHint annotation. It does not mention potential side effects like file creation or overwriting, whether it requires an existing KiCad project, or what happens on success/failure. This is a significant gap for an import tool.

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, concise sentence that front-loads the core action without redundant words. However, it is too sparse to fully support agent decision-making, but for what it covers, it is well-structured.

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 an import tool with side effects, no parameter descriptions, and a rich set of sibling import tools, the description is extremely incomplete. It omits prerequisites, output handling, error scenarios, and interaction with the KiCad project, leaving the agent with insufficient information.

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?

With 0% schema description coverage, the description must explain parameters but only hints that geda_pcb_path is the input file and output_dir is the output directory. It does not clarify defaults, formats, or relationships, leaving the agent to guess.

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 imports a gEDA PCB into a KiCad project directory. It uses a specific verb ('Import') and names the resource ('gEDA PCB') and destination, distinguishing it from sibling import tools like mfg_import_allegro and mfg_import_pads.

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 provides no guidance on when to use this tool versus alternatives, no prerequisites, and no exclusions. It simply states the function without context on selection criteria or expected input/output.

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