delete_sheet

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

Discloses destructiveness, snapshotting behavior, formatting not restored, and force parameter. Lacks authorization or rate limit info, but given no annotations, it is thorough enough.

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?

Concise with a clear summary followed by details and argument list. Slightly verbose but well-organized.

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 destructive tool with no output schema, it covers behavior, defaults, snapshotting, and edge case (large sheets). Complete enough for safe agent usage.

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 0% schema coverage, the description explains all parameters: spreadsheet_id_or_url, sheet, dry_run (default TRUE), and force, adding meaning beyond the schema.

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 clearly states 'Delete an entire sheet' with a specific verb and resource, distinguishing it from sibling tools like clear_range or 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?

Provides guidance on dry_run default and how to actually delete, plus force parameter. Does not explicitly compare to alternatives but implies safe exploratory usage.

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