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

Annotations already declare readOnlyHint=true, so the safety profile is covered; the description usefully adds the shape of the response, which matters because no output schema exists. It says nothing about scope limits, however — whether trashed files, shared drives, or file contents are searched is left unstated, and no pagination or default-limit behavior is mentioned.

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?

Two short sentences, zero filler, with the core operation front-loaded and the return payload immediately after. Every clause carries information an agent would otherwise have to guess at.

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 low-complexity read-only tool with 100% schema coverage, annotations, and an enumeration of return fields, the definition is close to sufficient. The remaining gap is search scope — which corpora and whether trashed items are included — plus any signal separating this from the recent-files sibling.

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 100%, with the query parameter documenting Drive query syntax and examples and page_size documenting its default of 20, so the baseline is 3. The description adds no parameter-level meaning beyond the schema — it never mentions the query syntax, the account selector, or paging.

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?

States a specific verb and resource ('Search for files in Google Drive') and adds what comes back ('file names, IDs, types, and modification dates'), so the agent knows exactly what operation this is. It does not distinguish itself from the close sibling gws-mcp__drive_list_recent_files or explain when search beats that alternative.

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?

Usage is only implied by the word 'search' — an agent can infer it is for locating files by criteria, but there is no explicit when-to-use statement, no exclusions, and no routing versus drive_list_recent_files or drive_get_file. A single clause naming the alternative would have moved this to a 4 or 5.

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