List Google Spreadsheets

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering safety and idempotency. The description adds that the tool lists spreadsheets the user has access to, which is useful but not extensive. No contradictions; thus score 3 for adding some value beyond annotations.

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 a single, clear sentence that immediately states the action and resource. No unnecessary words, efficiently front-loaded with the key purpose.

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 listing tool with well-documented parameters, annotations covering safety, and an output schema provided, the description is nearly complete. It could hint at the output structure or pagination, but the current version is adequate and leaves minimal ambiguity.

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?

Parameter schema coverage is 100% with complete descriptions in the schema. The tool description adds no additional details about parameters (max_results, user_google_email). Baseline score of 3 is appropriate as no extra meaning beyond schema is provided.

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 spreadsheets from Google Drive that the user has access to', specifying the verb (list), resource (spreadsheets), and scope (accessible to user). It explicitly differentiates from siblings like create_spreadsheet, get_spreadsheet_info, and search_drive_files by focusing on listing user-accessible spreadsheets.

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?

No guidance is provided about when to use this tool versus alternatives. Siblings like 'search_drive_files' and 'list_drive_items' exist, but the description does not offer selection criteria or constraints, leaving the agent without usage context.

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