Replace Chemdraw Objects In Office

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

With no annotations provided, the description carries full responsibility for behavioral disclosure. It hints at mutation ('replace') and preserving position ('without moving them'), but omits crucial details like whether the input file is modified in place, what output_path does, the effect of render_pdf_preview, or any side effects or reversibility.

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 a single sentence with no redundancy, but it is under-specified. While concise, it sacrifices essential information, making it inadequately detailed for a tool of this complexity.

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?

Given the tool is a mutation operation with 4 parameters, no annotations, and no output schema, the one-sentence description is grossly incomplete. It lacks the manifest format, selection mechanism, output handling, preview behavior, and any error or edge-case information.

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%, and the description does not mention any of the four parameters. It provides no explanation of input_path, output_path, render_pdf_preview, or replacements_manifest, leaving the agent to infer meaning solely from names and types.

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 verb ('Replace'), a clear resource ('selected ChemDraw OLE contents and previews'), and a scope ('selected'), while also noting a key constraint ('without moving them'). This distinguishes it from sibling tools like inspect (read-only) and embed (add new).

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?

No guidance is given on when to use this tool versus alternatives. It does not mention when to prefer it over inspect_chemdraw_objects_in_office or embed_cdxml_in_office, nor does it state any prerequisites or exclusions.

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