apply_hwp_paragraph_style

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

Without annotations, description discloses internal mechanism (adds paraPr, retargets paraPrIDRef) implying file modification. Lacks mention of error handling or idempotency, but covers main behavioral traits.

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 very concise sentences. First states overall purpose, second lists arguments with details. No unnecessary words; front-loaded with key 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?

Covers main behavior and parameters well. Missing details on default behavior when output_path omitted, error conditions (e.g., invalid paragraph_index), and file permissions. Adequate given 6-param complexity and no output schema.

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 0%, but description explains all 6 parameters: specifies align enum values, notes 'any subset' of formatting options, and clarifies optionality of output_path. Adds meaning beyond raw schema types.

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?

Clear verb 'apply' and resource 'paragraph formatting' with specific attributes (alignment, indent, line_spacing) and target (Nth paragraph in .hwpx). Distinguishes from sibling `apply_hwp_text_style` by focusing on paragraph-level formatting.

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?

Lists arguments and their roles, including optionality and allowed align values. Does not explicitly compare with siblings or state when not to use, but provides sufficient guidance for parameter selection.

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