clear_formatting

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

The annotation 'destructiveHint: true' already signals this tool modifies the document. The description adds that it clears formatting, which aligns with the annotation. However, it does not disclose other behavioral details such as whether the action is reversible, whether it saves automatically, or how it handles partial selection. It adds minimal value beyond the annotation.

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, front-loaded sentence with no wasted words. Every part contributes to explaining the tool's purpose and coverage.

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?

Despite having 8 parameters and no output schema, the description is minimal. It does not explain return behavior, confirmation, or what happens when 'paragraph_ids' is omitted (clears from all paragraphs is left implicit but is in the schema). More context about the destructive nature and expected outcome 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?

The input schema has 100% description coverage for all 8 parameters, each explained clearly. The tool's description only summarizes the types of formatting cleared (bold, italic, etc.), which is already evident from the parameter names and descriptions. It does not add meaningful semantic value beyond the schema.

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 ('Clear specific run-level formatting') and the resources ('paragraphs'), listing the specific formatting types (bold, italic, underline, highlight, color, font). It effectively distinguishes from siblings like 'format_layout' which likely deals with paragraph-level formatting.

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 provides no guidance on when to use this tool versus alternatives. It does not mention scenarios where clearing formatting is appropriate, prerequisites, or when other tools (e.g., 'format_layout') might be better suited. The agent receives no decision-making context.

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