wps_word_set_paragraph_format

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

No annotations are provided, so the description carries full burden for behavioral disclosure. It does not mention side effects, idempotency, permissions, or what happens when no parameters are set. As a formatting setter, it is likely non-destructive, but this is not stated. The description adds no behavioral context beyond the action itself.

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 a single short sentence that front-loads the purpose and enumerates key parameters. Every word contributes meaning; there is no redundancy or filler.

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 5 optional parameters, no annotations, and no output schema, the description should cover more context: behavior when multiple parameters conflict, defaults, impact of the 'range' parameter (selection vs all), and whether the tool returns anything. The current description is insufficient for an agent to reliably use this tool without additional inference.

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 the baseline is 3. The description briefly lists the parameters (段前/段后间距, 行距, 首行缩进) in a condensed form, which mirrors the schema properties. It adds no additional constraints, default values, or usage nuances beyond what the schema already provides.

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 action ("设置") and resource ("段落格式"), and enumerates the specific formatting properties (段前/段后间距, 行距, 首行缩进). This distinguishes it clearly from sibling tools like wps_word_set_font or wps_word_set_alignment.

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 when paragraph formatting is needed, but provides no explicit guidance on when to use this tool versus alternatives, no prerequisites, and no excluded scenarios. The distinction from siblings is implicit through the listed properties.

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