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

Annotations already declare the operation read-only, idempotent, closed-world, and non-destructive, so the safety profile is covered. The description adds non-obvious behavioral scope: results are limited to "owner-restorable" items (not everything archived) and include purge deadlines, which tells the agent the listing will surface retention pressure.

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 no filler and no repetition of the title. Every clause (list, archived roots, owner-restorable, purge deadlines) carries distinct information.

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 described; with zero parameters and full annotation coverage the description only needs to convey scope and it does. Minor ambiguity remains around "roots" (whether descendants are excluded) and result ordering/pagination, which the description leaves 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?

The tool takes zero parameters and the schema coverage is 100%, so there is nothing for the description to disambiguate. Baseline 4 applies; no parameter detail is needed or missing.

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 ("List") plus a precisely scoped resource: archived sheet AND folder roots, restricted to "owner-restorable" items, returning purge deadlines. An agent can distinguish this from siblings such as sheets_list, sheets_list_folder_page, and sheets_restore without opening any schema.

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?

Usage is implied by the qualifiers: you call this to discover archived items that are still restorable before a purge deadline. However, with ~60 siblings including sheets_restore and sheets_restore_folder, the description never states the follow-up or the when-not (e.g., use sheets_list for live sheets).

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