reject_all_changes

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

The description explains the effect of rejecting changes (removing insertions, restoring deletions), which adds behavioral context beyond no annotations. However, it does not disclose if the action is irreversible or require any document state, leaving room for ambiguity about safety.

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 at two sentences, front-loading the core action and then explaining the effect. Every sentence is necessary and no words are wasted.

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?

Given the simplicity of a parameterless tool with an output schema, the description adequately explains the tool's action and effect. However, it could mention that the document must have tracked changes enabled, which would improve completeness.

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?

There are zero parameters, so schema coverage is 100%. The description provides sufficient meaning for a parameterless tool, explaining what the tool does without needing to elaborate on parameters.

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 rejects all tracked changes, specifying that insertions are removed and deletions are restored. This directly distinguishes it from siblings like 'accept_all_changes' and provides a specific verb+resource purpose.

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 gives no guidance on when to use or avoid this tool. It does not mention prerequisites (e.g., track changes must be enabled) or alternatives. No explicit usage context is provided.

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