render

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions out_path for pdf and normalize, hinting at file writes, but does not describe permissions, side effects, reversibility, or output behavior for any action.

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 compact line with no filler, and the capability list is front-loaded before the action-parameter mapping. It is terse to the point of being cryptic, but every token serves the dispatch purpose.

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 seven actions, nine parameters, no annotations, and no output schema, the description is too thin. It maps actions to parameters but leaves action semantics, return values, and behavioral constraints largely unexplained.

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 only 33%, so the description must compensate. It does add useful action-parameter mapping (e.g., pdf uses out_path and optional pages, page_image uses page and optional dpi), but it does not explain the meaning, format, or constraints of most parameters.

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 identifies the tool as a Hangul engine and lists seven operations (PDF, page image, check, layout, update_fields, view, normalize), but it does not state an overarching purpose in a clear verb+resource sentence. It also provides no differentiation from sibling tools such as convert, image, or page.

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 offers no explicit when-to-use guidance, no conditions for selecting this tool over alternatives, and no named alternatives from the sibling list. Usage is only implied by the action list.

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