list_sheet_tables

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

No annotations provided, so description carries full burden. It implies read-only behavior via 'list' and mentions the OAuth scope, but does not disclose potential limitations like pagination, rate limits, or behavior when no tables exist. Adequate but not comprehensive.

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 concise sentences: first for core purpose, second for clarification, third for usage guidance and scope. No unnecessary words, well structured and front-loaded.

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?

Tool is simple with only 2 required parameters and an output schema present. Description covers purpose, usage hint, and scope. Could briefly mention that output is a list of tables, but the existence of output schema makes this acceptable. Overall sufficient.

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?

Input schema has 100% description coverage, so schema itself fully documents parameters. Description adds no extra semantic detail beyond the schema, meeting baseline but not exceeding.

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?

Description clearly states it lists all structured tables (native Sheets tables) in a spreadsheet, distinguishing them from bounded ranges. It also notes the primary use case of discovering table_id for append_table_rows, making the purpose highly specific and actionable.

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 tells when to use the tool (to discover table_id before append_table_rows) and notes the required OAuth scope. However, it does not mention when not to use or provide alternatives, slightly limiting completeness.

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