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

Annotations already cover safety (destructiveHint=false), idempotency, and closed-world scope, so the bar is lower; the description still adds real value by disclosing what is NOT carried over (history, sharing) and that the copy gets its own ownership. It omits what happens to folder placement or whether the copy needs a name.

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?

Two sentences, front-loaded with the action and scope, then the exclusions. No filler or restatement of the title.

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 idempotency. The copy/exclusion semantics are present; only destination placement and any naming or permission requirements for the resulting sheet are unaddressed.

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 50% (idempotencyKey is richly documented, sheetId has none). The description hints that sheetId identifies a 'readable' source sheet, adding a permission implication, but gives no naming, placement, or output-target semantics beyond that.

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?

Specific verb (duplicate) plus resource (sheet), with scope defined as the 'current state' and the result framed as an 'independently owned sheet'. It also implicitly distinguishes itself from copy-type siblings by stating that historical versions and sharing are excluded.

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?

The description gives no when-to-use guidance, no prerequisites, and does not name any alternative such as sheets_create, sheets_copy_column, or sheets_transfer_ownership. The agent must infer that this is the tool for producing a standalone full-sheet copy.

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