excel_duplicate_sheet

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

Annotations include destructiveHint: true, but description doesn't clarify if duplicate overwrites an existing sheet or creates new. Also lacks details on what is duplicated (formulas, formatting, etc.). The description adds minimal 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?

Single sentence, no waste. Efficient but slightly too brief, sacrificing clarity.

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?

Given 4 parameters, no output schema, and a large sibling list, the description is incomplete. Missing behavior on duplicate name conflicts, return value, and backup implications.

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 covers 3 of 4 parameters with descriptions (75%). The description adds no extra meaning beyond schema. The createBackup parameter lacks description and is not explained in the description.

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?

Description states 'Duplicate a complete sheet', which is a verb+resource. It clearly distinguishes from siblings like create_sheet, delete_sheet, rename_sheet. However, it doesn't specify 'complete' means all content/formatting or if duplication stays within the same file.

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 on when to use versus alternatives like creating a new sheet and using copy_range. No mention of conflict behavior or prerequisites.

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