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

With no annotations, the description carries the full burden of behavioral disclosure. It clearly states the operation is non-destructive to formatting and rows, and adds a human-interaction requirement (confirm before clearing). It does not mention effects on formulas, data validation, or permissions, but the core behavior is well disclosed.

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?

Two sentences, no redundancy. The primary action is stated first, and the user-confirmation safety note is appended without clutter. All words earn their place.

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?

The description covers the core behavior but omits crucial context: parameter format (e.g., 'range' syntax like A1:B2), prerequisites (workbook/sheet existence), and any impact on formulas or calculations. With no output schema and low parameter schema coverage, this is insufficient for reliable invocation.

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 only 25% (only mailbox has a description), and the tool description provides no additional parameter information. The description does not explain how to specify 'range', 'sheet', or 'workbookId', leaving the agent to guess naming conventions and formats. This is a significant gap for a low-coverage 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 states a specific verb ('Empty') and resource ('the values in a range'), and clarifies it leaves formatting and rows intact, distinguishing it from row deletion or value replacement. The tool name and title also differentiate it from clear_google_sheet_range and update_excel_range.

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 the use case: clearing values while preserving formatting and row structure. It includes a safety guideline about confirming before clearing user data, but does not explicitly name alternatives or state when to prefer this over update_excel_range or clear_google_sheet_range.

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