gws.sheets.list_tabs

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds a valuable behavioral detail: that returned content is wrapped in <untrusted-document-content> tags and should not be treated as instructions. This goes beyond annotations and helps prevent prompt injection issues.

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 two sentences long, front-loaded with the core purpose, and the security note is a meaningful addition. No redundant or vague wording is present; 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?

For a simple read-only list tool with comprehensive schema coverage and annotations, the description is complete. It states the return fields (title, sheet ID, grid dimensions) and includes a critical security warning. No output schema exists, so the description adequately covers what the agent needs to know.

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%, so the baseline is 3. The description does not add extra meaning to the parameters beyond what the schema already provides. It does mention 'spreadsheet' but not the 'account' parameter, so the schema remains the primary source of parameter semantics.

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 specific action: 'List the tabs (sheets) in a Google Spreadsheet with title, sheet ID, and grid dimensions.' This uses a specific verb ('List'), specifies the resource (tabs in a spreadsheet), and distinguishes it from sibling tools like read_range or write_range.

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 implies usage by stating what the tool does but does not explicitly explain when to choose this over alternatives or mention any exclusions. Given the sibling context, the purpose is clear enough for an agent to infer, but no explicit guidance is provided.

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