chemdraw_add_symbols

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

Beyond the annotations, the description discloses that the source is unchanged, output goes to a new absolute directory, placement is bounded and can fail on collision/unsupported geometry, before/after exports and audit are produced, and no complete mechanism validation is promised. This gives an agent a clear behavioral model of a write-producing tool.

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 dense but front-loaded: the main action appears first, and every subsequent sentence adds a distinct constraint or caveat. There is no filler or repetition of the schema.

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 8-parameter tool with no output schema, it covers the new-copy semantics, failure conditions, review requirement, and output artifacts. The main gaps are the unmentioned optional rendering parameters and the absence of an explicit statement of what the tool returns (e.g., audit location or export paths).

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?

With 0% schema description coverage, the description must document parameters. It explains the symbols array structure, output_dir, and hints at expected_source_token, but it leaves span, pixels, clearance, and line_width unexplained; their meanings must be guessed from names. Clearance is only obliquely referenced by 'bounded outward placement'.

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 first sentence names a specific action and resource ('Add native symbols to a NEW copy') and restricts the payload to explicit {key, kind, atom_id} requests. It also contrasts the operation with chemical edits and radical-state edits, which separates it from related sibling tools like chemdraw_edit_document or chemdraw_annotate_document.

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?

It gives a clear prerequisite ('Inspect current IDs/token first') and tells the agent this works on a copy, requires a new absolute output directory, and needs visual/chemical review. It does not explicitly name alternatives or state when not to use the tool, but the 'not a chemical edit' wording provides an implicit exclusion.

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