workiva_delete_sheet

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

No annotations are given and the description merely says 'Delete a sheet'. It does not disclose whether deletion is permanent, whether there are cascade effects on other data, or if special authorization is required. For a destructive operation, this level of transparency is insufficient.

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 extremely concise, front-loaded with the action, and presents parameters in a clean list. Every sentence provides necessary information without excess.

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?

The core operation and parameter meanings are covered, but the description lacks contextual details such as permanence of deletion, potential dependencies, or error handling. Since an output schema exists, return values need not be described, but behavioral context for a destructive action is missing, making it minimally adequate.

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?

With 0% schema description coverage, the description compensates by explaining both parameters: spreadsheet_id is 'The spreadsheet UUID' and sheet_id is 'The sheet UUID to delete'. This adds meaningful type and role information beyond the bare schema property titles.

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 a specific verb 'Delete' and resource 'a sheet from a spreadsheet', clearly distinguishing it from sibling tools such as create_sheet, copy_sheet, list_sheets, and get_sheet. The purpose is unambiguous and directly stated.

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?

No guidance is provided on when to use this tool versus alternatives, nor any warnings about irreversible deletion or required permissions. The description only states the operation without contextual usage advice.

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