sheets_get_spreadsheet

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

With no annotations, the description carries the behavioral burden and does disclose key traits: grid data is off by default, enabling it returns formatting, and range restriction mitigates large-spreadsheet cost. It stops short of stating auth requirements or account-resolution behavior (which the schema covers for email).

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?

Three tight sentences, front-loaded with what the tool returns, followed by default-behavior and discovery guidance. No filler; every sentence carries actionable content.

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?

There is no output schema and no annotations, so the description is the main source of truth, and it covers return contents, the grid-data default, and ID discovery adequately. Auth/permission behavior is the only notable gap, which the email parameter description partially offsets.

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 75%, so the schema already documents each parameter thoroughly (including the URL/gid caveat and email rules). The description adds only a light performance rationale for 'ranges' and the formatting motive for grid data, so it sits at the high-coverage baseline of 3.

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 ('Get') and resource ('spreadsheet') and enumerates exactly what is returned: metadata, tab titles/IDs, dimensions, named ranges. The scope note that cell grid data is excluded implicitly separates it from sheets_read_values, so an agent can distinguish it from siblings without opening a 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?

Gives clear operational guidance: enable grid data only for formatting needs, restrict ranges for large spreadsheets, and discover IDs via drive_search_files with the specific mimeType filter. It lacks an explicit 'use sheets_read_values instead when you need cell values' exclusion, but context for when to reach for this tool is solid.

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