chemdraw_export

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

Adds meaningful behavioral context beyond the basic annotations: refusing overwrites, offline resvg rasterization for PNG, and explicit failure without rasterizer fallback. The annotations only say readOnlyHint=false, openWorldHint=false, destructiveHint=false, so this extra disclosure is valuable. No contradiction detected.

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?

Three dense sentences pack in the tool's identity, a crucial overwrite behavior, PNG-specific processing details, a hard prerequisite, and a failure mode. Every sentence carries distinct information with zero 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?

For a moderate-complexity export tool with no output schema, the description covers the prerequisites, key options, and failure behavior sufficiently for an agent to invoke it correctly. The only notable gap is that it does not describe what a successful call returns, but this is not essential for making the call.

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 explains 'pixels controls longest side' and implies path is a file whose parent must exist. However, document_id is left to inference, and format is covered only by the enum. It adds some semantics but does not fully compensate for the coverage 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?

The description states a clear verb+resource: export a document through actual ChemDraw, and adds a key behavioral constraint ('refusing overwrites'). It does not explicitly differentiate from the sibling chemdraw_batch_export, which is the natural alternative, leaving some ambiguity about scope.

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 explicit when-to-use guidance or named alternatives. The description does provide useful prerequisites ('Output parent must exist') and a limitation ('Unsupported SVG resources fail explicitly'), but it never tells an agent when to pick this tool over batch_export or another sibling.

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