Returns the Markdown extension and JSON block syntax for writing HWPX document content, so you can build the exact formatting the template expects.
내용 작성 문법(Markdown 확장 / JSON 블록)을 돌려준다.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v2.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so the description carries full burden. It implies a read-only reference lookup but never states that it performs no mutation, requires no inputs, or returns static documentation content. The only behavioral hint is '돌려준다' (returns), which is 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?
Single efficient sentence that front-loads what is returned. Appropriately sized for a zero-parameter reference tool, though it could be slightly more explicit about the tool's role.
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?
A zero-param, no-output-schema reference tool is simple, but in a 10-tool family the description doesn't clarify its role relative to hwpx_start_here or when an agent should reach for it. Adequate but leaves a real gap around usage context.
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?
Zero parameters, so baseline is 4. There is nothing to document and the description correctly implies no input is needed.
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?
States a specific return ('내용 작성 문법' - content authoring syntax, Markdown extension / JSON block). However, it's a guide/returns-syntax tool whose purpose is largely tautological in a tool list ('format guide returns format syntax'). Doesn't clearly distinguish from sibling hwpx_start_here, which likely also covers authoring guidance.
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?
No guidance on when to use this vs alternatives. With siblings like hwpx_start_here, hwpx_build, and hwpx_convert_hwp, an agent needs to know this is a reference/lookup tool, not an action tool, and when to invoke it. None of that is stated.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.