com_import_pdf

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

With no annotations, the description carries the full burden and does so thoroughly. It discloses the invisible Word instance, default output location, refusal to overwrite existing files, package-level validation, OCR limitations, and the explicit warning on near-zero word count.

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 efficient and front-loaded with the core action, then expands to output behavior, validation, and caveats. Every clause provides necessary information without repetition or filler.

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 conversion tool with no annotations, the description covers the operation, output handling, failure safety, validation, and realistic limitations. It gives an agent enough to select and invoke the tool correctly without needing to inspect internals.

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?

The input schema has 0% description coverage, so the description must compensate. It explains the output_path default behavior and existing-file refusal, and it makes clear the required pdf_path is the source PDF. It could tie the semantics to parameter names more explicitly, but it adds meaning well beyond the bare schema.

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 names a specific action ('Convert a PDF to .docx') with the mechanism ('Word's built-in PDF reflow') and the resource involved. It clearly distinguishes this from the sibling com_export_pdf by stating the directionality (PDF to .docx, not .docx to PDF).

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 clear context for when conversion is appropriate by distinguishing text-based PDFs from complex layouts and scanned image PDFs. It does not explicitly name an alternative tool for unsupported inputs, so it stops short of full when-not guidance.

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