hwp_insert_row_at_cursor

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

No annotations, so description carries burden. Discloses error condition, position meanings, and that it inserts relative to cursor. Lacks mention of side effects or formatting impact, but for a simple row insert, this is adequate.

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?

Three sentences, front-loaded with main action. Includes version info which is minor but not overhead. Could be slightly trimmed but overall efficient.

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?

Simple tool with 1 param and no output schema. Description covers error condition, position mappings, sibling distinction. Adequate for invoking correctly.

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% with parameter description already explaining enum values. Description adds only slight rephrasing ('표 맨 끝' for append). Minimal additional value beyond 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?

Description clearly states verb '행을 추가합니다' (insert row) with resource 'cursor-based cell'. Distinguishes from sibling hwp_table_add_row by mechanism (cursor vs table_index). Includes version note and error condition.

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?

Explicitly compares to hwp_table_add_row, saying this tool is for cursor-based insertion and that alternative uses table_index. States '표 바깥이면 에러' (error if outside table) and gives use case: '사용자가 "여기에 한 줄 더" 요청 시 유용'.

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