Add Heading to Document

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

With no annotations provided, the description carries the full burden. It discloses that the tool appends (a mutation) but lacks key behavioral details: whether the file must already exist, if the file is modified in place, what happens on error, or if the heading replaces existing content. This is a significant gap for a file-modifying 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 a single, informative sentence that is front-loaded with the core action and includes the most relevant customization options. No wasted words or redundant details.

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 an 8-parameter mutation tool with no output schema and no annotations, this description is minimally adequate. It covers the core purpose and highlights key parameters, but omits important context about file handling (e.g., creating vs. modifying), side effects, and failure behavior, which an agent would need to invoke it safely.

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 schema fully documents all 8 parameters. The description lists categories like font size, color, alignment, and RTL support but does not add new information beyond what the schema already provides. Baseline 3 is appropriate.

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 appends a styled Heading (H1-H6) to a Word document, specifying the resource (Word document) and the action (appending a heading). It distinguishes itself from sibling tools like add_paragraph_to_document by explicitly targeting headings with style customization.

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?

Usage is implied: use this tool when you need to add a heading to a Word document. However, there is no explicit guidance on when to prefer this over add_paragraph_to_document or other siblings, nor any exclusions or prerequisites beyond the obvious heading intent.

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