chemdraw_build_reaction_series

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

Annotations are all false (not read-only, not open world, not destructive), so the description carries the burden of behavioral disclosure. It discloses meaningful limits: no product inference, no balance certificate, support restricted to water/halides and bounded salts, and separate verification of native chemistry and layout. This goes well beyond the raw annotation fields and gives an agent a realistic picture of what the tool will and will not do. No contradiction with readOnlyHint=false, since 'Build' implies a write operation.

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 two dense sentences with no filler, and the primary action and key constraint ('1 through 3 explicitly supplied reaction rows') are front-loaded. The jargon ('bounded salts', 'native chemistry and measured layout verified separately') is compact but meaningful, so nothing feels wasted. Slightly dense readability keeps it from a 5.

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?

With 5 parameters, no output schema, and no per-parameter descriptions, the description explains the most complex input (steps and participants) and sets expectations about limits, which is valuable. However, it says nothing about layout, pixels, preset, or output_dir semantics beyond what their names imply, leaving the optional parameters underspecified. Adequate for the required inputs, but incomplete for fully informed invocation.

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 does clarify the steps array structure (step_id, reactants/products, optional above/below conditions) and participant fields (compound_id, label, smiles, optional positive coefficient), adding real meaning to the opaque schema. Yet layout, pixels, preset, and output_dir receive no explanatory attention, so the compensation is partial.

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 uses a specific verb ('Build') with a clear resource ('1 through 3 explicitly supplied reaction rows on ONE editable ChemDraw page'), and the series scope differentiates it from the sibling chemdraw_build_reaction. It also states what the tool does not do (no product inference or balance certificate), removing ambiguity about its role. The resource and constraints are precise enough for an agent to know when this tool applies.

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 implies usage for explicitly supplied multi-row reaction series (1-3 rows) on a single page, and the 'No product inference' note signals it is not for route design or inference. However, it never names sibling alternatives such as chemdraw_build_reaction or chemdraw_build_scope_job, nor states explicit when-to-use/when-not-to-use conditions. The guidance is only implicit.

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