hwp_image_extract

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

No annotations are provided, so the description carries the full burden. It states 'extract all images' but does not disclose potential side effects (e.g., creating directories, overwriting files) or error conditions (e.g., missing directory). The tool's read-only nature is implied but not confirmed.

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 consists of two concise sentences, each serving a clear purpose: stating the main function and providing usage guidance. There is no unnecessary information or repetition.

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 simplicity of the tool (1 parameter, no output schema, no annotations), the description is minimal but covers the core functionality. However, it lacks details about return values, error handling, or whether the directory is created automatically. For a complete tool definition, additional context would be beneficial.

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% (only parameter 'output_dir' has a description). The tool description merely references '지정 디렉토리' which aligns with the schema. No additional semantic information about the parameter format, validation, or default behavior is provided beyond the 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 clearly states 'Extract all images from the document to the specified directory' with a specific verb and resource. It also provides a usage scenario: 'Use when importing images from document as files'. This distinguishes it from sibling tools like hwp_insert_picture or hwp_set_background_picture.

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 explicitly says when to use the tool: '문서 내 이미지를 파일로 가져올 때 사용하세요.' This is clear guidance. However, it does not mention when not to use or provide alternatives, but the context is sufficient for an AI agent.

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