search_drive_files

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

With no annotations provided, the description carries the full burden and largely delivers. It discloses the return format ('formatted list of found files/folders'), pagination behavior via nextPageToken, and the conditional interaction between drive_id and corpora. It also documents behavioral defaults for page_size, include_items_from_all_drives, and detailed. Minor omissions: no mention of rate limits or auth requirements, though the required user_google_email implicitly signals authenticated access.

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 purpose sentence is front-loaded and followed by a disciplined Args/Returns structure. Every parameter entry earns its place because the schema provides no descriptions, so the length is appropriate rather than bloated. There is no filler, repetition, or irrelevant detail.

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?

Operationally complete for a complex 9-parameter tool with interacting parameters (drive_id ↔ corpora ↔ include_items_from_all_drives), covering defaults, pagination, filtering, and output format; an output schema also exists. The gap is tool-selection context: how search_drive_files relates to list_drive_items, search_docs, or get_drive_file_content is never addressed, which matters given the extensive sibling list.

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?

At 0% schema description coverage, the description fully compensates by documenting all 9 parameters with meaning beyond bare type/default. file_type even enumerates accepted friendly names and gives a raw MIME example; drive_id and corpora explain conditional behavior and preferred values; page_token explains how to paginate. This is exemplary compensation for a schema that carries no descriptions.

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: 'Searches for files and folders within a user's Google Drive, including shared drives.' The scope qualifier ('including shared drives') adds useful precision beyond a generic search statement. However, it doesn't explicitly differentiate from siblings like search_docs or list_drive_items, so it misses the top criterion for a 5.

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 on when to choose this tool over siblings such as list_drive_items or search_docs, and no exclusions or conditions are stated. The only directional advice is parameter-level ('Prefer 'user' or 'drive' over 'allDrives' for efficiency'), which addresses argument choice, not tool selection. With over 100 sibling tools, an agent must infer when a query-based search is the right entry point.

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