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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered structurally. The description adds the shape of what is returned (title, tab, used range in A1, framing Sheet element), which is useful context but largely overlaps the output schema and does not disclose pagination, ordering, or size 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?

Two sentences, both earning their place, with the core purpose front-loaded and the workflow linkage trailing. Slightly dense phrasing in the parenthetical but no redundancy or 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 and full parameter coverage, the description need not explain return values or parameter shapes, and it covers purpose and the read_sheet/change_sheet handoff. It is sufficient for a simple read-only list tool; a note on behavior for documents with many sheets/tabs would make it fully complete.

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 description coverage is 100%: documentId and tabId are both documented in-schema. The description adds no format, default, or filtering semantics beyond what the schema already provides, so the baseline 3 applies.

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 (List) and resource (a document's sheets) and immediately distinguishes itself from read_sheet and change_sheet by describing them as consumers of the titles returned here. An agent can tell this apart from sibling tools 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?

The closing sentence establishes the workflow context: call this first to obtain sheet titles, which read_sheet and change_sheet then accept. That is clear routing guidance, though it stops short of explicit 'use this instead of X when...' exclusions or prerequisites for other siblings.

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