Modify WordprocessingML XML Element

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

With no annotations provided, the description must carry the full burden of behavioral disclosure. It identifies the target (document.xml) but omits critical details such as whether the modification is in-place or uses outputPath, whether invalid XML could corrupt the document, or any prerequisite knowledge needed. This is a significant transparency gap for a low-level 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 a single, well-front-loaded sentence that immediately establishes the verb, resource, and purpose. Every word earns its place, with no redundancy or filler.

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 a low-level tool with no annotations and no output schema, the description is too minimal. It does not explain the tool's side effects, the meaning of outputPath, or how to use it safely. Given the complexity of raw XML modification, more context is needed to prevent misuse.

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 the baseline is 3. The description adds no extra parameter meaning beyond what the schema already provides, aside from a generic mention of text nodes/tags, which aligns with targetText/replacementText but does not enhance understanding.

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 specific action ('Performs low-level XML text node or tag modification') and the exact resource ('document.xml'), distinguishing it from sibling tools that operate at higher levels of abstraction. The phrase 'for deep customization' reinforces its unique role.

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?

The description implies usage for 'deep customization' but does not explicitly state when this tool should be preferred over siblings or when it should not be used. No alternatives are named, and the guidance remains implicit rather than explicit.

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