hwp_apply_style_profile

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

With no annotations, the description must be transparent. It discloses that it repeatedly calls set_paragraph_style, indicating it modifies paragraph styles. However, it does not explain handling of table_styles or title_styles in the profile, leaving ambiguity about the full effect on the document.

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: first states primary purpose, second adds context about input source and implementation. No unnecessary words, front-loaded with the main 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?

Given the sibling tools and no output schema, the description covers the input relationship and implementation. It could clarify the effect on non-paragraph elements, but overall it is complete enough for an agent to use correctly.

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% with descriptions. The description adds value by explaining that the profile is the output of hwp_analyze_writing_patterns and that the tool internally calls set_paragraph_style, which helps understand how the parameters are used.

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 it applies a 'formatting pattern profile (WritingPatterns)' to the current document, with the verb 'applies' and a specific resource. It distinguishes itself from siblings like hwp_apply_style (single style) and hwp_set_paragraph_style (individual style) by referencing the profile input and repeated calls.

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?

It specifies that the tool uses the output of hwp_analyze_writing_patterns as input, providing clear usage context. It does not explicitly state when not to use it, but the close coupling with the analysis tool implies a workflow, which is sufficient.

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