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

With no annotations provided, the description carries the full burden. It discloses that the deletion is permanent and cascades to all tabs, which are critical behavioral traits. It does not mention permissions or side effects, but the key implications are 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?

The description is a single sentence, front-loaded with the verb 'delete', and contains no redundant words. It efficiently conveys the full scope of the action.

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 one-parameter delete tool, the description fully covers the purpose, scope, and irreversibility. No output schema is needed, and the sibling context provides adequate alternatives for comparison.

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 schema already covers the parameter with a description 'Sheet (workbook) ID'. The tool description adds some context about deleting the entire workbook, but this is more about behavior than parameter semantics, providing minimal additional value 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 uses the specific verb 'permanently delete' and clearly identifies the resource as 'spreadsheet (sheet, excel, workbook)' with the scope 'and all its tabs'. This distinguishes it from siblings like delete_sheet_tab and delete_document.

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 implies when to use this tool by stating it deletes the entire workbook including all tabs, making it apparent that delete_sheet_tab would be used for a single tab. However, it does not explicitly name alternatives or provide exclusion criteria.

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