hwp_insert_auto_num

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

No annotations are provided, so the description must disclose behavioral traits. It fails to indicate whether the operation is safe or destructive, what document elements are affected, or if there are prerequisites. The one-line description gives no behavioral insight.

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 short sentence, making it concise but under-specified. While front-loaded, it sacrifices necessary detail for brevity. It could include a brief example or scope without losing conciseness.

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 complexity of the sibling tool set (many insertion tools) and the absence of an output schema or annotations, the description is incomplete. It does not specify where numbering is inserted, what type, or any side effects, leaving significant gaps for an AI agent to infer.

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 input schema has zero parameters, so schema coverage is 100%. The description adds no parameter-level detail because there are none. However, it does not clarify what 'auto numbering' entails, such as default behavior or formatting, which would be helpful baseline context. A score of 3 reflects adequate but not enhanced semantics.

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 '자동 번호매기기를 삽입합니다.' (Inserts automatic numbering) identifies a specific verb and resource, but 'auto numbering' is ambiguous—could refer to list numbering, heading numbering, or other constructs. This vagueness, especially given many sibling insertion tools like hwp_insert_caption or hwp_insert_page_num, reduces clarity.

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 provides no guidance on when to use this tool versus alternatives. With over 80 sibling tools including many insertion operations, the lack of contextual cues forces the agent to guess the appropriate scenario.

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