Manage tabs

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

Annotations already declare readOnlyHint=false, destructiveHint=true, and openWorldHint=true, so the safety profile is covered. The description adds almost nothing beyond that: it does not warn that delete irreversibly removes the tab and its data, nor does it mention the account/auth requirements, so it earns little credit over structured fields.

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?

A single tight sentence that front-loads the verb list with no filler. It is appropriately sized for the tool, though the terseness leaves behavioral context unstated rather than wasteful.

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 7-parameter, multi-action, destructive mutation tool with no output schema, the description is thin: it never explains how the parameters interact per action (e.g., tab + new_name for rename/duplicate, rows/columns only for add) or the account default behavior. The rich schema compensates substantially, making this minimally adequate.

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 86%, so the schema itself documents tab, rows, columns, new_name, account, and spreadsheet semantics. The description only restates the action list and adds no format, default, or interaction detail (e.g., tab vs new_name for duplicate), so baseline 3 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 names a specific resource (tab/sheet) and enumerates four concrete verbs matching the action enum (add, delete, rename, duplicate). It is clearly distinguishable from siblings like insert_rows_or_columns or delete_rows_or_columns that operate on cell ranges rather than whole tabs, though it never explicitly routes the agent away from 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?

There is no explicit when-to-use or when-not-to-use guidance, and no mention of alternatives such as create_spreadsheet for a new file or delete_rows_or_columns for clearing data. The agent must infer selection purely from the action enum, which the schema already provides.

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