Add, rename or delete a sheet tab

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

Annotations already indicate destructiveHint=true, but the description goes far beyond: it warns that deleting destroys everything, requires confirmation with confirmCells, explains the last-tab restriction and its workaround, and states that every action is read back before being reported. This is excellent behavioral disclosure with no contradictions.

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 dense but every sentence earns its place. It front-loads the purpose, then systematically walks through actions, error handling, safety mechanisms, and fallbacks. No fluff, well-organized, and easy to parse.

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?

Given the tool's complexity (three actions, confirmation, destructions, last-tab edge case) and lack of output schema, the description is remarkably complete. It covers all key behaviors, error paths, and alternatives, leaving no obvious gap for an agent to call it correctly.

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?

With only 38% schema coverage, the description compensates well by explaining action values, tab identifiers, and confirm/confirmCells semantics in the delete flow. However, it does not explicitly clarify sheetUrl or spreadsheetId, and confirm's role in rename/add is left implicit. The description adds meaning but does not fully cover all eight parameters.

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 clearly states the tool adds, renames, or deletes a tab in a Google Spreadsheet. It distinguishes itself from siblings like list_sheet_tabs by specifying the three mutation actions, making its purpose 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 gives explicit patterns for each action ('action:"add" + title', etc.), explains tab identification by title or sheetId, and details the delete confirmation flow. It also names alternatives (clear, or delete_drive_file for the last tab) and notes error handling with the real list, providing comprehensive usage guidance.

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