Manage Sheet Tab

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

Annotations already flag destructive and non-read-only behavior, and the description adds a meaningful behavioral boundary: it mutates the tab itself rather than content, and enumerates the possible lifecycle operations including delete. It does not elaborate on consequences such as data loss or authorization, but the destructiveHint plus schema coverage keep this from being a serious gap.

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?

Three short sentences: the first front-loads the core purpose, the second names the two sibling alternatives, and the third states scope. No fluff or repetition of schema fields.

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 rich 100%-covered schema, an output schema, and annotations indicating destructiveness, the description supplies the one thing an agent cannot infer reliably: when this tool is the right lifecycle tool versus create_sheet or resize_sheet_dimensions. Nothing needed to safely select and invoke it 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?

With 100% schema description coverage, the schema already documents all six parameters, including action-specific requirements like new_name for rename and new_index for reorder. The description does not add parameter-level detail, so the baseline 3 is appropriate.

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 precise operation set (rename, delete, hide, unhide, reorder) applied to an existing sheet tab, so an agent immediately knows what the tool does. It goes beyond the name by adding a resource boundary and naming create_sheet and resize_sheet_dimensions to differentiate sibling scope.

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?

It explicitly routes tab creation to create_sheet and row/column changes to resize_sheet_dimensions, and closes with 'This tool operates on the tab itself' as an exclusion rule. This gives an agent a clear when-to-use/when-not-to-use decision without opening the schemas.

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