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

Beyond the annotations (destructiveHint=true, idempotentHint=true, readOnlyHint=false), the description discloses the non-obvious behavior: nothing is cleared on the first call, the count is returned, and confirmation requires echoing that count. It explains the safety purpose of the echo, the lack of a default range, and the read-back verification. This is rich, non-redundant behavioral context that significantly exceeds the annotations.

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 dense paragraph but every sentence serves a purpose: purpose, destructive warning, protocol, rationale for echo, no default, verification, alternative. It is front-loaded with the core purpose and progressively details the safety flow. It could benefit from slight structural breaking (e.g., bullets), but remains efficient and free of fluff.

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 tool with a mandatory safety protocol, the description covers all essential operational steps: the two-call flow, confirmCells echo, read-back verification, and the alternative for tab removal. It also explains the return value context (filled-cell count) on first call. The absence of an output schema is mitigated by this description. Nothing critical for correct invocation is missing.

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 40% (range and confirmCells have descriptions). The description adds meaningful semantics to confirmCells (echo the filled-cell count) and range (no default, explicit). However, it offers no explanation for sheetUrl or spreadsheetId, which lack schema descriptions. Since coverage is low and these remain unexplained, the description only partially compensates for the 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?

The description opens with a specific verb and resource: 'Empty a range of cells in a Google Sheet, leaving the rows themselves in place.' It clearly distinguishes from the sibling manage_sheet_tabs by explicitly stating the alternative for removing a tab, making the tool's scope unambiguous.

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 explicit when-to-use guidance, detailing the mandatory two-step confirm protocol: first call without confirm to get the filled-cell count, then call again with confirm:true and confirmCells set to that count. It also names the alternative tool (manage_sheet_tabs) for removing a whole tab, leaving no ambiguity about when to choose this tool.

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