list_spreadsheets

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

With no annotations, the description carries full responsibility. It discloses sorting order, required OAuth scope (drive.readonly), and that the returned ID feeds other tools. It does not detail pagination or exact output, but an output schema exists. It could be more explicit about 'accessible' meaning spreadsheets the user has access to, but overall is transparent.

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 key purpose and ordering, then use case, alternative, and scope. Every sentence adds value, with no wasted words.

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 list tool with two parameters and an output schema, the description is complete. It covers purpose, usage guidelines, behavioral traits (ordering, scope), and provides an alternative. No gaps are apparent.

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 coverage is 100%, so both parameters are described in the schema. The description adds no additional information about the parameters beyond what the schema provides. Baseline 3 is appropriate as the schema does the heavy lifting.

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 states 'List accessible Google Sheets spreadsheets' with ordering 'most-recently-modified first', clearly specifying the verb and resource. It distinguishes from the sibling tool search_drive_files by mentioning that for a broader search by name, the sibling should be used.

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 explicitly says 'Use this as a discovery step when the user only has a spreadsheet name', providing when to use the tool. It also gives an alternative: 'For a broader Drive search by name use search_drive_files with file_type="sheet"', offering clear when-not and alternative guidance.

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