delete_sheet

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

Since no annotations are provided, the description must fully disclose behavioral traits. It states the action and return message but omits whether the deletion is permanent, irreversible, or requires special permissions. The verb 'Delete' signals destructiveness, but the lack of any caution or side-effect disclosure is a notable 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?

The description is compact and well-structured, with a one-sentence purpose, an Args section, and a Returns section. Every sentence provides necessary information without redundancy or filler.

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 two-parameter deletion tool, the description adequately covers the action, parameters, and return value, and the output schema can fill in the response structure. The main omission is explicit mention of irreversibility or side effects, which is relevant for a destructive operation.

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 0%, so the description carries the full burden for parameter meaning. It compensates well by explaining spreadsheet_id as the spreadsheet ID and sheet_id as the numeric sheet ID from list_sheets, adding valuable context beyond the bare schema property names.

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 'Delete a sheet from a spreadsheet,' which clearly states a specific verb and resource. This distinguishes it from sibling tools like delete_rows and delete_columns, which operate on cells.

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 mentions that sheet_id comes from list_sheets, which is a useful prerequisite. However, it does not explicitly state when to use this tool versus alternatives such as delete_rows or duplicate_sheet, leaving usage context implied rather than fully specified.

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