wps_word_set_font

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

No annotations are provided, so the description must disclose behavioral traits. It only states that bold/italic accept true/false. It fails to mention side effects, whether it modifies existing formatting, prerequisites (e.g., an open document), or what happens when parameters are omitted. This is insufficient for a mutation tool.

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 short and to the point, consisting of two sentences. It conveys core info efficiently with no wasted words. Could benefit from a slightly more structured presentation but remains concise.

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?

With 5 parameters, no output schema, and no annotations, the description is too minimal. It does not clarify that all parameters are optional, how omitting parameters affects formatting, or what the tool returns. Lacks context for an AI agent to fully understand its behavior.

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 Chinese descriptions for each property. The description adds minimal value beyond the schema—it repeats the range values and notes bold/italic accept true/false. Baseline 3 applies as schema already does the heavy lifting.

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's purpose as setting font formatting. It adds explanation for the 'range' parameter values. However, it does not differentiate from sibling tools like wps_word_set_alignment or wps_word_set_paragraph_format, which handle other formatting aspects.

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?

No explicit guidance on when to use this tool versus alternatives. The description implies it's for font properties but lacks when/when-not instructions or references to other related tools among siblings.

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