extract_cdxml_from_office

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It explains the extraction process, the conversion to CDXML, output directory behavior, the return dictionary structure, and failure semantics ('publish nothing on partial failure'). This exceeds what would be expected for a simple extraction 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 relatively long but well-structured into logical sections (purpose, technical detail, requirements, args, returns, safety). The purpose is front-loaded, and every sentence contributes value (e.g., file format internals, transactionality). A minor deduction for verbosity that could be tightened.

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?

The description is complete for an extractor tool with no output schema. It details supported inputs, conversion backends, dependencies (olefile), output directory default, return keys, and failure handling. An agent has everything needed to call it correctly without additional inference.

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%, yet the description fully compensates by specifying the file path types ('a .pptx, .docx, .xlsx, or .xls file') and the output_dir default ('a folder named "<basename>_chemdraw/" next to the input file'). This adds semantic meaning beyond the bare schema field names.

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 clearly states a specific verb ('extract'), a specific resource ('embedded ChemDraw objects from a PPTX, DOCX, XLS, or XLSX file'), and differentiates from sibling tools like convert_cdx_cdxml (file format conversion) and extract_structures_from_image (image extraction). The scope is unambiguous.

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 scopes usage to office files and explains the underlying storage (ZIP vs OLE2) for each format, which helps an agent understand when this tool applies. It does not explicitly name alternatives to avoid, but the format-specificity combined with sibling tool names provides adequate guidance.

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