hwp_set_paragraph_style

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

With no annotations, the description carries full burden. It discloses auto-correction behavior for negative indent and version-specific features, but lacks details on side effects, permissions, or whether it affects only one paragraph or multiple. Mutation is implied but not explicitly stated as non-destructive.

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 very concise: two sentences and a version note. Key formulas and version details are front-loaded. Every sentence earns its place with minimal waste.

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?

Despite high parameter count (31) and no output schema, the description provides high-level context for core behavior but lacks overview of all parameter groups (e.g., borders, line spacing). It doesn't mention return values or success/failure. Version notes are helpful but not comprehensive.

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 each parameter has a description. The tool description adds value by explaining the relationship between left_margin, indent, and first line position, and by noting auto-correction and aliases (first_line_indent). This extra context aids understanding.

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 changes paragraph formatting at the current cursor position, using a specific verb and resource. It explains key parameters (left_margin, indent) with formulas. However, it does not distinguish from siblings like hwp_apply_style, which applies predefined styles.

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 modifying paragraph properties at cursor but provides no explicit when/when-not guidance. It mentions version requirements (v0.6.7+) for borders, but no alternatives or exclusions are offered.

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