list_sheets

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

With no annotations, the description carries the burden of conveying behavior. It mentions the return format and 'all sheets' scope, but does not explicitly state that the operation is read-only or has no side effects. The verb 'List' strongly implies safe reading, but this is not made explicit.

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 extremely concise and well-structured with a one-sentence summary followed by Args and Returns sections. Every sentence adds value, with no redundant information.

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 with an output schema, the description covers purpose, parameter, and return value adequately. There are no hidden complexities or side effects that need further elaboration.

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 provides no description for spreadsheet_id, but the tool description adds a clear definition ('The ID of the spreadsheet'). This fills the schema coverage gap and provides essential meaning for a single 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 the tool's function with a specific verb ('List all sheets/tabs in a spreadsheet'). It is distinct from sibling tools like get_spreadsheet_info, which focuses on spreadsheet metadata, and other sheet operations.

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 when to use the tool (when you need to enumerate sheets) but does not explicitly compare to alternatives or mention exclusions. There is no 'use X instead' guidance, so usage context is inferred rather than stated.

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