Workbooks Duplicate Workbook

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=true, so the write-but-non-destructive profile is covered structurally. The description adds useful behavioral facts: that `name` is required by the API and that omitting destination_folder_id clones into the original's folder. It still says nothing about permissions, whether the original is touched, or rate limits.

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?

One lead sentence plus three tight per-parameter lines, front-loaded with the action before the details. No filler.

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?

With an output schema present, return values need no explanation, and all three parameters are documented despite 0% schema coverage. The only real gap is selection guidance against sibling copy/create tools.

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 0%, so the description must carry all parameter meaning, and it does: it explains workbook_id, name (with API-required note), and destination_folder_id (with default semantics). This meaningfully compensates for the undocumented schema, though it omits format/ID conventions.

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 opens with a specific verb+resource ("Duplicate an existing workbook"), which is clearer than a generic create. However, it does not differentiate itself from the closest sibling, workbooks_copy_workbook_to_member, which also copies a workbook, so an agent must still infer the distinction.

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 explicit when-to-use guidance or naming of alternatives (create_workbook, copy_workbook_to_member, create_workbook_from_template). The only contextual rule given is the destination-folder default, which is more parameter behavior than usage guidance.

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