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

Annotations already declare the safety profile (non-read-only, non-destructive, non-idempotent), and the description adds real value: it lists what content is copied, states the permission requirement, and specifies the default name and uniqueness constraint. It does not state what happens if a copy with a colliding name already exists or whether the source sheet is affected.

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?

Front-loads the action and the copied-content scope, then packs default naming, uniqueness, and permissions into a compact block. The trailing "Signature:" line partially repeats the schema but is cheap and aids fast invocation.

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?

An output schema exists, so return values need not be explained, and annotations cover the mutation profile. The description covers permissions, naming defaults, and copied content; only edge-case behavior (name collisions, missing sheet) is unstated.

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 67%, with file_uuid undocumented in the schema; the description compensates by giving the full signature and by adding semantics for new_name (default value and uniqueness requirement). Sheet and new_name are already described in the schema, so it does not fully exceed a solid baseline.

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?

Names a specific verb and resource ("Duplicates a sheet") and enumerates exactly what is carried over (cells, formats, code, tables). It does not explicitly differentiate itself from siblings such as sheets_create or sheets_rename, which keeps it short of a 5.

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?

"Requires edit permission" gives one concrete prerequisite, and duplicating within a file is implied by the parameters. There is no explicit when-to-use versus sheets_create/sheets_rename, and no guidance on what happens if the sheet does not exist.

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