delete_worksheet

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

The annotation already discloses destructiveHint: true, and the description adds no extra behavioral context such as whether deletion is permanent, what happens to references, or error conditions. It merely restates the action, providing no value beyond the annotation.

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 concise sentence with no unnecessary words. It is efficiently structured for a simple tool, though it omits potentially useful details.

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, the description is too sparse. It lacks information about return values, error handling, prerequisites, and what happens to the worksheet's contents. The annotations cover the destructive aspect, but the overall context is incomplete for an agent to understand the full impact.

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 fails to explain 'filepath' and 'sheet_name'. While the names are somewhat self-explanatory, the description does not clarify how these parameters are used (e.g., file path format, workbook structure). The description thus does not compensate for the lack of parameter documentation.

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 and resource: 'Delete worksheet from workbook.' This clearly states the tool's function and distinguishes it from sibling tools like create_worksheet or rename_worksheet. However, it could be more precise by specifying permanence or scope.

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?

There is no guidance on when to use this tool vs. alternatives such as hiding a worksheet, clearing contents, or deleting rows. The description simply states the action without providing context on appropriate scenarios or prerequisites.

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