Delete spreadsheet tab

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

No annotations are provided, so the description carries the full behavioral burden. It correctly discloses destructive, irreversible behavior with 'Permanently delete,' which is critical for a mutation tool. However, it omits permission requirements, side effects on existing data, and any recoverability limits.

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 front-loaded sentence with no filler or redundancy. It is appropriately sized for the core purpose, though its brevity contributes to gaps in usage and safety context.

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 three-parameter destructive tool with full schema coverage and no output schema, the description conveys the core action and permanence. It still lacks usage boundaries and safety context, but the schema covers invocation details and no return-value explanation is needed.

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 description coverage is 100%, and the schema itself documents spreadsheetId, sheetId (including that it comes from google_sheets_get metadata), and account. The description adds no additional parameter-level meaning, so the baseline of 3 for high schema coverage applies.

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 states a specific verb ('delete') and resource ('tab (sheet) from a spreadsheet'), and 'permanently' clarifies the operation's irreversible nature. It also implicitly distinguishes this tab-level deletion from siblings like add_sheet, rename_sheet, and delete_rows.

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?

There is no guidance on when to use this tool versus alternatives such as google_sheets_add_sheet, google_sheets_rename_sheet, or google_sheets_delete_rows. Prerequisites such as obtaining the numeric sheetId from get metadata are only in the schema, not the description.

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