batch_export

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

No annotations are provided, so the description carries full burden. It states it processes directories and converts files, but does not disclose whether it modifies originals, handles errors, or requires permissions. Basic behavioral traits are implied but not fully detailed.

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 three sentences, front-loaded with the core action. It is efficient but could be slightly tighter by removing 'Essential for...' which is not strictly necessary.

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 complexity (batch operation with nested parameters) and presence of an output schema, the description adequately covers the main purpose. However, it lacks details on output behavior, error handling, and directory structure preservation, leaving some gaps.

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 coverage is 100%, so baseline is 3. The description mentions directories and target format but adds no specific parameter details beyond what the schema already provides (e.g., recursive, format_type, file_patterns).

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 does batch export of multiple SolidWorks files to a target format, mentioning processing entire directories. This distinguishes it from single-file export tools like export_step or export_pdf, as it emphasizes batch and directory-level operation.

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 usage context: project migrations, supplier deliverables, and large-scale conversions. It implies use when handling multiple files, but does not explicitly state when not to use or compare to alternatives like batch_process_files.

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