merge_hwp_cells_vertical

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

The description discloses the core operation: setting rowSpan and removing absorbed cells. However, it does not clarify mutational behavior regarding the output_path (whether it overwrites the original file if omitted) or error conditions, which are critical for safe use.

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 two sentences: the first explains the operation, the second lists arguments concisely. It is front-loaded and contains no fluff.

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 lack of annotations and output schema, the description should cover behavior on missing files, return values, and error handling. It does not address these, leaving significant gaps for a mutation tool with 6 parameters.

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 description lists parameters with one constraint (row_count >= 2) and one optional note (output_path). With 0% schema coverage, this adds some meaning, but it omits definitions like indexing starting point (0-based?) and other parameter 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 clearly states the tool's function: merging vertical cells across rows in a single column using rowSpan. It distinguishes from the sibling tool 'merge_hwp_cells_horizontal' by specifying vertical merging.

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 lists arguments and notes row_count >= 2, but does not provide guidance on when to use this tool over alternatives (e.g., horizontal merge). It lacks context on prerequisites like table existence or column validity.

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