hwp_apply_document_preset

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

No annotations provided. Description states the action (apply batch) but does not disclose side effects (e.g., overwriting existing formatting, reversibility, or prerequisites). Limited behavioral insight beyond the core operation.

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, front-loaded with action. No redundant information. Could potentially list presets more efficiently, but overall concise and clear.

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?

For a simple tool with one parameter and no output schema, the description covers what it does, what it applies, and eligible values. Lacks error conditions or result confirmation but adequate for typical use.

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 parameter description listing allowed values. The description adds meaning by explaining what each preset does (paper settings + font/line spacing), going beyond the schema's label-only description.

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 document presets with paper settings and font/line spacing, and lists the six preset names. This distinguishes it from siblings like hwp_apply_style or hwp_set_page_setup.

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 applying a complete preset but does not explicitly state when to use vs. alternatives (e.g., listing presets first via hwp_get_preset_list). No exclusions or when-not-to-use guidance.

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