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

Beyond the destructiveHint annotation, the description discloses critical behaviors: deletion destroys data and requires a confirm step, unknown tabs are refused with a real list instead of a cryptic error, Google disallows removing the last tab, and every action is verified by reading back from the spreadsheet. These are non-obvious operational details an agent needs, and they exceed what annotations alone convey.

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 and well-structured, with action examples first, then safety warnings, then verification note. Every sentence adds value—no fluff. It is slightly long, but the content justifies the length. A very concise 4.

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 all actions, identifier resolution, deletion confirmation, and edge cases. The one notable gap is it never mentions how the spreadsheet itself is identified (sheetUrl or spreadsheetId), which are present in the schema. Since those are likely needed for any call, this is a minor omission. Overall quite complete for a complex 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?

With schema description coverage at only 38%, the description compensates thoroughly. It maps action to the required companion parameters (title, tab+newTitle, tab), explains tab can be title or sheetId, and clarifies the confirm/confirmCells pair for deletion. It gives meaning to almost every parameter that matters, despite the schema being sparse.

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 clear verb-resource pairing: 'Add, rename or delete a tab in a Google Spreadsheet.' It explicitly enumerates the three actions and ties parameters to each, and distinguishes the tool from siblings like create_sheet (whole file) and delete_drive_file (file-level deletion). The purpose is unmistakable.

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 usage patterns for each action (e.g., 'action:"add" + title'), tells the agent to use list_sheet_tabs to obtain tab identifiers, and provides a two-step confirmation workflow for deletion. It also explains when deletion is impossible (last tab) and suggests alternatives. This is exemplary when-to-use guidance.

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