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

Annotations already disclose non-readonly, non-idempotent, non-destructive and open-world behavior, so the description only needs to add context. 'Append' usefully signals that the heading goes at the end of the existing content, but it does not say whether a missing file is created, whether a built-in Heading style is applied, or what happens on repeated calls.

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?

A single front-loaded sentence with zero wasted wording, and the level range is placed immediately after the core action so the agent can act on it at a glance.

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 no output schema and annotations already covering the safety profile, the definition is minimally sufficient for a simple mutation. However, it omits whether the document must exist, where the heading is inserted, and the styling effect, which matter for a write tool that appends to a file.

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 100%, so all three parameters are already documented in the schema, and the description only repeats the 1-6 level range. Baseline 3 applies since the schema does the heavy lifting and the description adds no format or default details.

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 a specific verb (append) and resource (section heading) scoped to a Word document, and the parenthetical 'level 1 to 6' makes clear this is a heading, not a plain paragraph, which separates it from the sibling add_paragraph. It stops short of explicitly naming that sibling, so it is clear but not fully differentiated.

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?

There is no when-to-use or when-not-to-use guidance; it does not say to prefer add_paragraph for body text or add_heading for structure, and it does not state prerequisites such as whether the target .docx must already exist. Usage is only implied by the word 'append'.

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