set_paragraph_format

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

With no annotations, the description carries full behavioral burden and does it well. It discloses live-editing behavior, keys that are refused while live, the auto-backup mechanism in `.ks4w-backups`, `backup=False` semantics, and atomic validated saving. It also explains that `outline_level: null` removes the override without touching style or visual formatting.

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 dense but front-loaded, beginning with the core action and target. The outline_level explanation and backup sentence are packed with important context, though the backup sentence is somewhat compressed and could be structured more cleanly.

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 complex tool with a nested formatting object and no annotation safety net, the description covers the key inputs, operation, live limitations, backup behavior, and a differentiating use case. It stops short of fully specifying allowed value sets for all formatting keys, but an output schema exists to absorb return-value details.

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 description coverage is 0%, so the description must compensate. It adds useful semantics: indices are 0-based, it lists the meaningful formatting keys, and it explains the outline_level range, null behavior, and backup flag. It does not define accepted values for keys like alignment or line_spacing, or clarify the `live` parameter's value semantics beyond 'auto'.

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 starts with a specific verb and resource: 'Set paragraph formatting on a batch of paragraphs' using '0-based indices.' It also distinguishes itself from `apply_style` by explaining when outline_level should be used without changing style/visual formatting, and names `get_paragraph_format` as the matching reader.

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 gives an explicit usage scenario for `outline_level`: assigning template headings a place in Word's navigation pane and TOC harvesting where `apply_style` would change their look. It also notes live-editing restrictions. However, it does not broadly contrast with other paragraph-related tools such as `format_text` or `replace_paragraph_text`.

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