set_formatting

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

The description mentions 'tracked-change markup', revealing that changes are tracked. However, with no annotations, it fails to disclose other behavioral traits like whether the tool modifies the document, requires an open document, or how it handles existing formatting. The tracked-change insight is useful but incomplete.

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 concise sentence, front-loading the key action. It is efficient but could be improved by adding brief parameter details or usage context without becoming verbose.

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 tool's eight parameters (two required), no schema description coverage, and many sibling tools, the description is too brief. It does not explain the required para_id and text arguments, the optional formatting flags, or the tracked-change behavior. The presence of an output schema is noted but not detailed, so the description leaves significant gaps.

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%, yet the description provides no explanation of any parameter. The schema includes eight parameters (para_id, text, bold, italic, underline, color, author, document_handle) but the description does not add meaning beyond the parameter names. The agent is left to infer semantics from types and names alone.

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 states it applies character formatting to text with tracked-change markup, which is a specific action. However, it does not distinguish this tool from siblings like set_run_color or set_run_font that apply individual formatting options. The phrase 'with tracked-change markup' hints at a unique feature but doesn't fully differentiate the tool's broader purpose.

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 guidance is provided on when to use this tool versus alternatives. Given many sibling tools for individual formatting properties, the description should indicate that this tool is for applying multiple character formatting options in one call or for tracked-change scenarios.

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