word_enable_track_changes

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

Discloses that python-docx changes after enabling will not be tracked, and directs to patch_with_track_changes. Annotations indicate readOnlyHint=false, which aligns with the mutating nature of the 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?

Concise, well-structured: summary, behavioral note, example, then Args/Returns. Every sentence adds value. Front-loaded with purpose.

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?

Covers all necessary aspects: purpose, behavioral constraint, parameter explanation via example, and return type. Adequate for a simple tool with good annotations and schema.

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 baseline is 3. The description adds an example with actual file path, clarifying usage, and explains return value (status message). Minor extra value.

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 enables Track Changes mode and distinguishes from sibling tool word_patch_with_track_changes, which handles programmatic tracked edits.

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?

Explicitly specifies when to use the tool (to enable tracking) and when to use an alternative (patch_with_track_changes for programmatic edits). Provides clear context.

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