hwp_verify_layout

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

No annotations are provided, so the description must fully disclose behavior. It states the conversion to PNG and path return but does not mention whether the operation is read-only, if the image is saved permanently, or any side effects. The PyMuPDF requirement is useful but insufficient for a full behavioral profile.

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 concise, front-loaded with the core action, and every sentence provides value: conversion purpose, visual verification benefit, usage context, and dependency. No wasted words.

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 simple parameter (one optional field) and no output schema, the description covers the main workflow (conversion, path, visual check). However, it omits details about the path (e.g., temporary or permanent), error conditions, and any prerequisites beyond PyMuPDF.

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 schema has 100% description coverage for the single 'pages' parameter, with examples and default behavior. The tool description adds no further param information, so a baseline score of 3 is appropriate.

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 the current document to a PNG image and returns its path, explicitly for visual verification of layout elements like table structure and cell merging. This distinguishes it from sibling tools like hwp_export_pdf (PDF export) and hwp_image_extract (extracting existing images).

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 a specific use case: 'Use for checking output after generating official documents.' It also notes the PyMuPDF dependency. However, it does not mention when not to use this tool or compare it to alternative verification approaches (e.g., hwp_verify_5stage).

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