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

The annotations already declare destructiveHint=true and readOnlyHint=false, so the destructive nature is known. The description still adds real value beyond them: it scopes the destruction (every row in the tab, not the file) and states the change cannot be undone through the API. It omits one notable edge case — the Sheets API rejects deleting a spreadsheet's last remaining tab — but otherwise the behavioral profile is covered.

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 tight sentences: what it does, what argument it needs, what it destroys, then two routings to alternatives. The destructive warning is capitalized and appears before the sibling routing, so the highest-risk information is front-loaded.

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 high-risk mutation with no output schema, the definition covers purpose, argument form, irreversibility, and alternatives — enough to call it correctly. The only gap is the last-tab constraint and the absence of any note on the response, though neither blocks correct invocation.

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 the baseline is 3; the description earns an extra point by specifying that the title argument is the tab's *current* title, which signals that a stale name after a rename will not resolve and that an ID or index is not accepted. It says nothing about the account parameter, but the schema handles that.

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 and resource ("Delete a tab (sheet) and everything in it from a spreadsheet") and immediately disambiguates it from two similarly named siblings, sheets_clear and sheets_delete, which differ by one word. An agent can pick the right tool without opening any schema.

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?

Gives explicit alternatives with the condition that selects each: sheets_clear to empty without losing the tab, sheets_delete to remove the whole file. It also implies the read-then-delete workflow by noting the tool takes the tab's current title.

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