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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the description need not restate danger; instead it adds real value by specifying what is destroyed (values only) versus preserved (formatting, rows) and by adding a user-confirmation workflow. It still says nothing about reversibility or how irrecoverable the cleared data is.

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 waste, and the payload-preserving constraint leads ahead of the confirmation advisory. Every clause earns its 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?

For a destructive, 3-required-parameter mutation with no output schema, the safety and preservation semantics are covered, but two of three parameters remain unexplained (notably range format) and there is no note on failure behavior for invalid ranges or missing permissions.

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 33%: mailbox is documented in the schema, while range and spreadsheetId carry no description at all. The description mentions "a range" but never gives A1 notation syntax or explains where spreadsheetId comes from, e.g. list_google_spreadsheets, so it fails to compensate for the coverage gap.

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?

Specific verb + resource ("Empty the values in a range") with a precise scope qualifier: formatting and the rows themselves are preserved. This separates it cleanly from clear_excel_range (different platform) and update_google_sheet_range (which writes rather than blanks values).

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?

Gives a clear usage condition, namely that the range's formatting should survive, plus a when-to-be-cautious rule (confirm before clearing anything the user did not just create). It does not explicitly route to a sibling such as update_google_sheet_range or delete-oriented tools, so it stops short of a full when/when-not/alternatives statement.

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