sheets_clear_range

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

Annotations already convey destructiveness, idempotency, and non-read-only behavior. The description adds important context beyond those annotations by specifying that cell formatting remains intact and that the operation clears only values. It also documents the return as a JSON confirmation string, which is useful behavioral information.

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 two short, purposeful sentences. The core behavior is stated first, followed by the return type, with no redundant or vague filler.

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 simple clear-range operation, the description combined with annotations and schema covers the essential information: what is cleared, what remains, that it is destructive yet idempotent, and the confirmation return. It does not discuss edge cases like invalid ranges or permissions, but that level of detail is not necessary for this tool.

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 tool description itself does not elaborate on individual parameters, but the input schema provides clear descriptions for both 'range' and 'spreadsheet_id', including format and source. Since the schema covers parameter meaning adequately, the description does not need to add more; a baseline score is appropriate.

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 specific verb 'clear' and resource 'range', and clarifies that only values are removed while formatting is preserved. This distinguishes it from siblings like sheets_write_range, sheets_append_values, and sheets_read_range, even without naming them.

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 when to use the tool (clear cell contents while preserving formatting) but provides no explicit alternatives or when-not-to-use conditions. An agent can infer the usage from the wording, but the tool does not proactively route to a sibling like sheets_write_range.

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