list_sheet_tabs

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

No annotations are provided, so the description carries the behavioral burden. It accurately describes a read-only listing operation and gives no indication of destructive side effects. It does not mention return ordering or error behavior, but the operation is simple and an output schema is present.

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 concise sentences with no filler. The core purpose is front-loaded, and the parameter guidance is directly attached without unnecessary detail.

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 one-parameter list operation, the description provides the necessary context: what the tool returns conceptually, why it is used, and how to obtain the required parameter. The presence of an output schema covers return-value details.

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 0%, but the description fully compensates by explaining that sheet_id is the target spreadsheet's ID from its URL and is required. This gives the agent the exact meaning and source of the only parameter.

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 a specific verb ('List') and resource ('tab (worksheet) names in a spreadsheet'), making the tool's purpose unambiguous. It does not explicitly name sibling tools for differentiation, but the list operation is clearly distinct from sibling tools like add_sheet_tab, rename_sheet_tab, and delete_sheet_tab.

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 provides clear context: use this tool to find the correct tab value before appending. It does not explicitly list exclusions or alternatives, but the usage intent is direct and actionable.

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