chemdraw_batch_export

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

Goes far beyond the sparse annotations (readOnlyHint=false, destructiveHint=false), disclosing that private copies are created and closed, errors stop later items without retry or closure of uncertain documents, failures are per-item, and outputs need human review. This is exceptionally transparent about side effects and edge-case behavior.

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 long but information-dense, with no filler. It is front-loaded with the core purpose, then systematically covers output, constraints, copy behavior, error handling, requirements, and caveats. Every sentence earns its place.

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 a complex batch operation with no output schema and minimal annotation support, the description covers most needed context: supported inputs, outputs, audit artifacts, error policy, and limitations. The missing 'pixels' semantics and lack of explicit return-value description keep it just short of complete.

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. It defines the items object structure precisely with key/source/formats, and clarifies output_dir as a new absolute output directory. However, the 'pixels' parameter is not mentioned at all, leaving a semantic gap.

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?

States a specific verb and resource: 'Sequential native batch export of explicit supported CDXML files.' It clearly signals batch operation, distinguishes itself from the singular sibling chemdraw_export, and enumerates the output contract (CDXML/SVG/PNG plus requested PDF/CDX).

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?

Provides clear when-to-use constraints: supported CDXML files, required chemistry extra, flat drawings plus a specific annotation subset, and rejection of unknown annotations. It also states what the tool does not do ('No style/layout/chemistry edits'), though it does not explicitly name an alternative sibling for single-file export.

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