list_spreadsheets

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

The description adds useful behavioral context beyond the readOnlyHint annotation, such as the default folder behavior when no folder_id is provided, which helps the agent understand the tool's operation.

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 concise with two main sentences plus structured Args/Returns sections, no unnecessary words, and front-loaded key 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?

The description covers the input parameter behavior, indicates the return structure (list of spreadsheets with ID and title), and is complete for a simple listing tool, especially with an output schema assumed present.

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?

Even though the input schema has 0% description coverage, the tool description provides detailed explanation of the folder_id parameter, including its optional nature and default behavior, effectively compensating for schema gaps.

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 'List all spreadsheets' with a specific resource and action, and it distinguishes from siblings like 'search_spreadsheets' and 'list_sheets' by focusing on listing vs searching or listing sheets within a spreadsheet.

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 explains when to use the tool (to list spreadsheets in a folder) and mentions optional parameter for folder selection, but it does not explicitly state when not to use it or compare to alternatives like 'search_spreadsheets'.

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