get_spreadsheet_info

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

Since no annotations are provided, the description carries full burden. It discloses the required OAuth scope (spreadsheets.readonly), states that it surfaces conditional format counts per tab, and explicitly states it does not read cell values. This covers safety and behavioral traits beyond the structured metadata.

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?

The description is four sentences, well-structured, and front-loaded with the core purpose. It then provides usage guidance and a clarifying note. Every sentence adds value without redundancy, making it highly efficient.

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?

Given the presence of an output schema (so return values need not be detailed), the description covers purpose, usage guidance, behavioral traits, and OAuth scope. For a metadata inspection tool, this is fully complete and leaves no gaps.

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 input schema has 100% parameter description coverage, so baseline is 3. The description adds minimal extra meaning for the parameters themselves, but does provide context that the output is metadata (title, locale, tabs, sizes). This is adequate but does not exceed expectations.

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?

The description clearly states it inspects spreadsheet metadata (title, locale, tabs, sizes) and distinguishes itself from siblings like read_sheet_values by noting it does not read cell values. It also lists specific sibling tools it supports (read_sheet_values, manage_sheet_tabs, protect_sheet_range), making its purpose unambiguous.

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 explicitly tells when to use this tool: to discover sheet names and sheetIds before calling certain sibling tools. It also clarifies what the tool does NOT do (read cell values), directing users to read_sheet_values for that. This provides clear guidance on appropriate use cases.

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