sheets_batch_delete_sheets

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

The description discloses the destructive action (deleting sheets) but adds no further context about irreversibility, error handling, or partial failures. The idempotentHint annotation provides some behavioral cue, but the description itself does not go beyond stating the obvious resource affected.

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 a single, well-structured sentence that front-loads the verb and resource. Every word earns its place, and there is no 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 batch-delete operation with only two parameters and no output schema, the description is sufficiently complete. It tells the agent what the tool does, and the schema fills in parameter details. The lack of a return-value explanation is not a concern given there is no output schema.

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?

The input schema covers 100% of parameters with descriptions, so the tool description does not need to add much. It adds no additional meaning beyond what the schema already provides, hence the baseline score of 3.

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 the action (delete), the resource (multiple sheets in a spreadsheet), and the batch nature ('in a single operation'). This distinguishes it from the sibling tool sheets_delete_sheet, which handles single-sheet deletion.

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 phrase 'in a single operation' provides clear context for when to use this tool (when deleting multiple sheets at once). However, it does not explicitly mention the alternative for single-sheet deletion or any exclusions, stopping short of a full 5.

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