search_drive_files

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

No annotations are provided, so the description carries the burden of disclosure. It adds the key behavior of searching across all accounts when omitted, and clarifies that it searches metadata (not content). However, it does not explicitly state that the operation is read-only, nor mention pagination, rate limits, or return format, leaving some gaps.

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 concise sentences. The first sentence front-loads the core purpose ('Search Google Drive file metadata'), and the second adds the important account-merging behavior without 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?

Given the tool's simplicity (3 parameters, no output schema), the description adequately covers what it searches (metadata) and a key behavioral nuance (account merging). However, it lacks explicit details about return fields, result ordering, or pagination, which would be useful for a tool that returns a list of files.

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?

The schema already provides 100% coverage of parameter descriptions, including the account-merging behavior in the account field. The description adds marginal value by clarifying that the search targets 'file metadata' rather than content, but this is not a major addition 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 the tool's function with a specific verb ('search') and resource ('Google Drive file metadata'). It distinguishes itself from siblings by specifying that omitting the account parameter searches all enabled accounts and merges results, which is a unique behavior not seen in list_drive_files or get_drive_file.

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 implies usage for searching file metadata, and the account-merging note provides practical guidance on when to omit the account parameter. However, it does not explicitly contrast this tool with alternatives like list_drive_files, so it stops short of fully explicit when-to-use guidance.

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