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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is covered. The description adds genuinely useful blast-radius information that annotations cannot convey: the entire subtree plus every active sheet within it is archived, and the 'owner-owned/owner-controlled' qualifier hints at an ownership prerequisite.

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?

A single front-loaded sentence with zero filler; the scope-defining clause is placed immediately after the core action.

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 no explanation, and the cascade scope is stated. However, for a destructive operation it omits the ownership/permission requirement, whether the action is reversible via sheets_restore_folder, and any partial-failure semantics when only some sheets qualify.

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 only 50%: idempotencyKey is fully documented in the schema, but folderId has no description at all. The description does not explain what folderId accepts or constrain it (e.g., must be a folder the caller owns), so it fails to compensate for the coverage gap.

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?

States a specific verb (Archive) and precise resource (folder subtree), and clarifies the cascade scope with 'all owner-owned active sheets inside it.' It implicitly distinguishes itself from sheets_archive (single-sheet) and sheets_restore_folder, though it never names those siblings.

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 when-to-use guidance, no prerequisites, and no mention of alternatives such as sheets_archive for a single sheet, sheets_restore_folder for reversal, or sheets_list_archived. The agent must infer selection from the name alone.

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