search_spreadsheets

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

The annotations already declare readOnlyHint=true, so the description's safety profile is clear. The description adds value by specifying search scope (name and content), but does not disclose rate limits, authentication needs, or behavior when results exceed max_results.

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 brief sentences for purpose, followed by clearly labeled Args and Returns sections. Every sentence provides value, and the structure is front-loaded for quick scanning.

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?

With 2 parameters (1 required) and an output schema present, the description adequately covers the tool's functionality. It explains what the tool does, how to use parameters, and the query scope. No missing critical context for a search tool.

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%, meaning the input schema provides only type and default. The description compensates by explaining the query searches in name and content with examples, and specifying max_results default (20) and max (100). This adds significant meaning beyond the schema.

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 'Search for spreadsheets in Google Drive by name or content', specifying the action, resource, and method. This distinguishes it from siblings like 'list_spreadsheets' (lists all) and 'find_in_spreadsheet' (searches within a specific 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 provides query examples and parameter limits, but does not explicitly state when to use this tool versus alternatives like 'list_spreadsheets' or 'find_in_spreadsheet'. It lacks guidance on exclusions or when not to use it.

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