hwp_table_delete_column

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

With no annotations provided, the description carries full responsibility. It states 'deletes current column' but fails to define what 'current' means (cursor position? selected column?). No disclosure of potential side effects like shifting remaining columns or data loss.

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?

Extremely concise: a single sentence that accurately conveys the tool's purpose. No wasted words.

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 simple operation and single parameter, the description is functional but incomplete. It lacks clarification on the meaning of 'current column' and does not mention that the tool presumably operates on the cursor's position. The presence of many sibling table tools makes this ambiguity more costly.

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%, so the baseline is 3. The description adds no extra meaning beyond the parameter's schema (integer, minimum 0). The term '표 인덱스' (table index) is already clear from 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 the action ('deletes') and the target ('current column from the table'). It distinguishes itself from the sibling tool 'hwp_table_delete_row' by specifying 'column' instead of 'row'.

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 tool versus alternatives like hwp_table_delete_row or hwp_table_add_column. The description does not mention prerequisites such as having a table selected or cursor position.

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