export_pos

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

With no annotations, the description carries the full behavioral burden. It does disclose that save_first saves the board before exporting, and it defines the allowed values for fmt and side. However, it omits key behaviors such as whether output_path is overwritten, whether the board must already be open, and any error conditions or side effects.

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 compact and front-loaded: the purpose appears in the first sentence, followed by a clear Args list. Every sentence contributes useful information, and there is no redundant 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?

The tool has 4 parameters, no annotations, and an output schema (so return values need not be explained). The description covers purpose and parameter meanings, but it lacks usage routing among sibling exports and deeper behavioral context such as overwrite behavior and preconditions, leaving gaps for an agent with no annotation support.

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 0%, so the description must compensate, and it does document all four parameters, including the allowed values for fmt ('csv', 'ascii', 'gerber') and side ('front', 'back', 'both'). It stops short of stating defaults (csv, both, true) or output_path format constraints, but it adds substantial meaning beyond the bare schema.

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 states a specific verb and resource: 'Export a component placement (pick-and-place) file.' This clearly distinguishes it from sibling export tools such as export_gerbers, export_bom, or export_step. An agent can immediately tell what this tool produces without opening the schema.

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?

There is no guidance about when to use this tool versus the many other export tools in the sibling list. It does not state prerequisites or conditions, such as requiring an open board or needing the board saved first. The argument list is informative but does not address usage context.

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