spreadsheet_delete_sheet

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

Annotations are absent, so the description bears the full burden. It discloses irreversibility ('This action cannot be undone') and the need to set confirm=true. However, it does not detail what happens when confirm=false (e.g., does it abort silently?) or error handling.

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 short sentences, front-loaded with purpose, then critical warning, then usage instruction. No unnecessary words.

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 and 5 parameters, the description covers irreversibility and confirmation but omits return values (presumably success/failure), error conditions, and potential side effects (e.g., broken references). Adequate but incomplete.

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 80%, and the description adds value by clarifying the relationship between file_id and name (alternatives) and the confirmation requirement. This goes beyond the schema's individual parameter descriptions.

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 verb ('Delete') and resource ('a sheet tab from a Synology Spreadsheet'). It differentiates from sibling tools like 'spreadsheet_add_sheet' and 'spreadsheet_rename_sheet' by specifying 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 description gives clear context for use: it is destructive and requires confirmation. It also tells to 'Provide either file_id or name' and 'Set confirm=true to execute'. However, it does not explicitly mention when to use this tool over alternative deletion tools like 'spreadsheet_delete_file'.

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