hwp_pdf_clone

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

With no annotations, the description fully carries behavioral disclosure. It details the engines used (PyMuPDF, PaddleOCR, pdfplumber), preprocessing steps (deskew, denoise, threshold), features like title detection, table reconstruction, image embedding, 2-column warning, fidelity score, and the output limitation (visually similar, not pixel-perfect). This is beyond minimal.

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 dense paragraph that front-loads the main purpose. Every sentence adds value, but it could be more structured (e.g., bullet points for features). It is not overly verbose.

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's complexity and absence of output schema, the description covers input types, internal processing, key features, and limitations. It misses a bit on output format details and error handling, but is largely complete for typical use.

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 coverage is 100%, so baseline is 3. The description does not add additional meaning to individual parameters beyond what the schema provides. It provides overall context but not per-parameter enrichment.

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 the tool converts PDF (native or scanned Korean) to editable HWP/HWPX files. This is a specific verb-resource-output combination, and it distinguishes itself from sibling HWP editing tools by being the only conversion tool from PDF input.

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 Korean PDFs and explains internal processing (native vs. scan, hybrid dispatch), but does not explicitly state when or when not to use this tool, nor does it provide alternatives. There is no exclusion criteria or comparison to other tools.

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