chemdraw_run_styled_job

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

The description adds meaningful behavior beyond the annotations: conflicting recipe settings are rejected, the actual package/hash is retained beside the output, native exports use ChemDraw, and numerical conventions do not substitute for chemical review. It does not disclose what gets created or overwritten or how errors are surfaced, but it reveals several important operational traits.

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 appropriately short and front-loaded with the core purpose. Every sentence adds information, though several phrases are compressed to the point of ambiguity (e.g., 'locked portable lab style', 'numerical conventions'), which slightly reduces clarity.

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?

This is a complex tool with four required parameters, an open recipe object, an enum workflow, and no output schema. The description provides only fragments: a CDXML requirement, a conflict-rejection rule, and a caveat about ChemDraw exports. It does not define the workflow values, recipe shape, style/packaging mechanics, or expected outputs, so an agent would need external knowledge to invoke it correctly.

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, but it only hints at recipe settings, a CDXML path, and output/package/hash behavior. It does not clarify the meaning of package_path, output_dir, the workflow enum values, or the structure of the recipe object, leaving four required parameters largely unexplained.

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 action, 'Run a native workflow', plus a key distinguishing constraint: the workflow uses a 'locked portable lab style'. It also names the grid/symbols workflow requirement, but 'native workflow' and 'locked portable lab style' remain somewhat jargon-heavy and the description does not explicitly differentiate from sibling build/apply/export tools.

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 gives useful context: this tool runs workflows with a fixed lab style, rejects conflicting recipe settings, and requires an input CDXML path for grid/symbols recipes. However, it does not explicitly state when to prefer this over sibling tools like chemdraw_build_scope_job or chemdraw_apply_route, nor what conditions would make it inappropriate.

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