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

With no annotations, the description carries the full burden, and it does well by disclosing that only values are emptied while formatting and rows remain, and by requiring user confirmation. It does not mention irreversibility or permission requirements, but the confirmation directive signals the destructive nature adequately.

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 concise sentences: the first states the core action and what is preserved, and the second gives a clear safety instruction. Every sentence earns its place and the most important behavioral detail is front-loaded.

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 purpose, the non-destructive-to-format behavior, and a confirmation requirement, which is solid for a simple clear operation. However, it omits the expected range syntax, how spreadsheetId should be supplied, and what a successful response looks like, leaving some gaps for an agent.

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% and the description does not compensate. It adds no format guidance for 'range' or 'spreadsheetId', and the word 'range' simply restates the parameter name. The 'mailbox' parameter is already described in the schema, so the description provides little additional parameter-level meaning.

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 uses a specific verb ('Empty the values') and resource ('a range') and adds a valuable nuance: formatting and rows are preserved. It is clear about what the tool does, though it does not explicitly distinguish itself from sibling tools such as clear_excel_range or update_google_sheet_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 instruction to ask the user before clearing anything they did not just create is a useful operational guideline. However, the description does not explicitly state when to choose this tool over alternatives or mention exclusion cases, so usage context is only implied rather than fully specified.

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