apply_hwp_paragraph_style

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

With no annotations, the description adds valuable behavioral details: it modifies header.xml by adding a new paraPr and retargets the paraPrIDRef. This discloses internal file structure changes, though it could mention handling of invalid paragraph indices or overwriting behavior.

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 brief and front-loaded with the core purpose. It uses a structured list for align values. One minor improvement would be to separate parameter details more clearly, but overall it is 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?

With 6 parameters, no output schema, and no error handling notes, the description provides a basic functional overview but lacks details on file_path format, paragraph_index bounds, units for indent/line_spacing, and return value. The internal file structure detail partially compensates.

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 schema has 0% parameter descriptions, so the description fully compensates by enumerating acceptable align values (LEFT|CENTER|RIGHT|JUSTIFY|DISTRIBUTE), clarifying that align/indent/line_spacing are optional subsets, and noting output_path is optional. However, file_path and paragraph_index lack format hints.

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 it applies paragraph formatting (alignment, indent, line_spacing) to a specific paragraph by index in an .hwpx file. The verb 'apply' and resource 'paragraph style' are unambiguous, and it distinguishes from sibling 'apply_hwp_text_style' which handles text-level styling.

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 implies usage for paragraph-level formatting but does not explicitly state when to use it over alternatives like 'apply_hwp_text_style' or 'set_hwp_paragraph_text'. No exclusionary conditions or context for use are provided.

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