sheets_delete_sheet

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

Annotations already declare destructiveHint=true, readOnlyHint=false, non-idempotent. The description adds that deletion is by sheet name, which is useful for identifying the target. However, it doesn't disclose irreversible data loss, required permissions, or what happens if the sheet doesn't exist. With annotations covering the safety profile, a 3 is appropriate – some added context but not rich behavioral detail.

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, front-loaded sentence with no wasted words. It clearly identifies the action, target, and scope.

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, the description is minimal but adequate given annotations cover safety. It could mention irreversibility or that the sheet must exist, but it provides sufficient information for an agent to invoke the tool correctly.

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 coverage is 100%, so both parameters (spreadsheet_id, sheet_name) are fully documented in the schema. The description reiterates that deletion is by name but adds no syntax, format, or constraints beyond the schema. Baseline 3 is correct when the schema does the heavy lifting.

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?

States a specific verb (deletes) and resource (sheet/tab from spreadsheet), clarified as 'by name'. This distinguishes it from sibling sheets_create_sheet and other delete tools like sheets_delete_chart. However, it doesn't explicitly note the sibling alternative or that deletion is by sheet name vs. index.

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 'from a spreadsheet by name' implies when to use it (to remove a tab), but there is no explicit when-to-use guidance, prerequisites, or mention of alternatives like clearing vs deleting. Usage is implied rather than stated.

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