drive_search

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

No annotations provided, so the description carries full burden. It does not disclose behavioral traits such as pagination (page_token), rate limits, authentication needs, result ordering, or whether the search is scoped to user's Drive. The description is too minimal for a tool that likely returns a list of files.

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?

Single sentence, no wasted words. It front-loads the main purpose. However, could be expanded slightly to cover the account parameter or pagination without losing conciseness.

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 complexity (4 parameters, search tool with output schema), the description is insufficient. It omits how to use page_token (pagination), the significance of account, and any search result format. While output schema covers return values, the description should guide parameter usage.

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 description adds meaning to 'query' (Drive query syntax) and 'mime_type' (optional MIME filter), but does not explain 'account' (required enum with two options) or 'page_token' (pagination). With 0% schema coverage, it partially compensates but misses important parameters.

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 searches Drive using query syntax and optionally filters by MIME type. It distinguishes from sibling tools like drive_get (single file retrieval) and drive_folder_create (creation). However, it doesn't specify the return type or scope (e.g., list of files matching query).

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 use this tool versus alternatives like drive_get or gmail_search. It doesn't mention prerequisites (e.g., account required) or scenarios where query syntax is appropriate. The description only states what it does, not when to choose it.

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