hwp_map_table_cells

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

The description reveals iteration order (Tab order) and that it returns a mapping of index to content. However, it does not disclose whether the tool is read-only, error behaviors, or performance implications. Since annotations are absent, the description partially carries the burden but lacks full transparency.

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?

Two sentences efficiently convey the purpose and usage context. No extraneous words; front-loaded with core action.

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?

The description covers the tool's purpose, usage scenario, and parameter. While it lacks explicit mention of output structure, the context of 'mapping' is sufficient for a simple tool. Slight room for improvement in specifying return format.

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 single parameter (table_index) is fully described in the schema (0부터 시작). The description does not add additional semantic value beyond the schema, but schema coverage is 100%, so baseline 3 is appropriate.

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 the action (iterating and mapping table cells in Tab order) and the specific resource (cells in a table). It distinguishes the tool from siblings like hwp_get_cell_format by focusing on Tab index mapping for use with hwp_fill_table_cells.

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 states when to use: for tables with merged cells to determine indexes for hwp_fill_table_cells. It provides a clear context but does not explicitly exclude other scenarios, leaving minor ambiguity.

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