docx.headers_footers_set

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

With no annotations, the description carries the full burden of behavioral disclosure. 'Set header/footer' reveals nothing about side effects, permissions, reversibility, or how the document is affected. For a mutation tool, this is severely insufficient.

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 concise to the point of being terse. It is extremely short, but this brevity comes at the expense of useful content. It is front-loaded but does not earn its place because it omits critical information that the tool's purpose and usage require.

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?

The tool appears to perform a significant operation on headers/footers, yet the description provides no context on how the target is specified, what parameters are expected (even implicitly), what the outcome is, or any relationships to other document parts. With no annotations or output schema, this is highly incomplete.

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?

The schema has zero parameters, so there is no parameter information to clarify. The baseline for 0-parameter tools is 4 because the description does not need to add parameter semantics. The description adds no parameter detail but none is needed.

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 names the action ('set') and resource ('header/footer'), which is clear at a basic level. However, it is ambiguous whether it sets content, style, position, or something else, and it does not distinguish from the similarly named list/get siblings beyond the obvious action difference.

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 given about when to use this tool versus alternatives like headers_footers_list or headers_footers_get, nor are there any preconditions or context clues. The description is a standalone imperative with no situational elaboration.

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