List the tabs in a Google Sheet

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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds 'Read-only, free,' reinforcing safety and cost behavior, plus explains its role as a discovery step. It doesn't contradict annotations and adds modest extra context beyond what annotations already provide.

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 efficiently convey purpose, usage guidance, and safety, with the core function front-loaded and no redundant content. Every sentence earns its place.

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?

Without an output schema, the description compensates by enumerating the fields returned (name, sheetId, row/column count, position) and explaining its role relative to other sheet operations. It provides all necessary context for correct invocation.

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 100%: both sheetUrl and spreadsheetId are described in the schema. The description does not add any new parameter semantics beyond what the schema already specifies, so baseline 3 is appropriate.

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 the tool lists tabs in a spreadsheet with specific fields (name, sheetId, row/column count, position). It also differentiates itself as a prerequisite for several sibling tools, making its purpose and scope 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?

Explicitly instructs when to call this tool: before naming a tab in update_sheet, clear_sheet_range, manage_sheet_tabs, format_sheet, and before proposing deletion. It also explains the reasoning (to learn actual content instead of guessing names), giving clear contextual guidance.

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