docx.changes_accept_all

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

With no annotations provided, the description carries the full burden of behavioral disclosure. 'Accept all tracked changes' implies a mutation, but it does not disclose whether changes are irreversible, whether the document must be saved afterward, or what impact it has on comments or other artifacts. This is a significant gap for a destructive operation.

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 extremely concise, consisting of four words with no redundancy. Every term is necessary, and the action-target structure is front-loaded. It does not waste space, though it could be expanded with additional context without losing conciseness.

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 simple single-parameter tool, the description could be more complete. It fails to mention whether the operation returns a success indicator, how errors are handled, or any prerequisites (e.g., open document). Given no output schema and no annotations, the description leaves critical execution details unspecified.

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 description coverage is 100%—docId is described as 'Document ID'. The tool description adds no additional meaning to this parameter; it only restates the resource being acted upon. Since the schema already minimally describes the parameter, a baseline of 3 applies.

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 action ('Accept') and the resource ('all tracked changes'), which directly conveys the tool's purpose. It distinguishes implicitly from other docx tools (e.g., docx.comments_delete, docx.replace_text), though it does not name an alternative or scope beyond accepting all changes.

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 provided on when to use this tool versus alternatives. It does not mention that accepting changes is a non-reversible operation, nor does it reference any related tools like docx.comments_list or docx.save. The agent receives no contextual cue about when accepting all changes is appropriate.

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