drive_list_files

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so the safety profile is covered. The description adds the returned field list and the 'Auto-approved' note, but that note is ambiguous (approval-free execution? pre-vetted call?) and no pagination or result-limit behavior is disclosed.

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 with the action and the return payload front-loaded; no filler. 'Auto-approved' is terse but its meaning is murky, slightly weakening an otherwise efficient structure.

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 no output schema, enumerating the returned fields is valuable and correctly done. But for a search tool it omits result-limit/pagination behavior, the meaning of the required 'reason' field, and any routing to sibling Drive tools, leaving clear gaps.

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 coverage is 67%; the query parameter is well documented in the schema itself (Drive 'q' syntax with examples and a doc link), so the description need not repeat it. However max_results has no description anywhere, and the description adds nothing about parameter semantics, so it sits at the baseline.

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 ('Search') and resource ('Google Drive files') and even enumerates the returned metadata fields (id, name, mime_type, owners, sharing status). It is distinguishable from drive_get_file_metadata and drive_list_folder by the 'search' framing, though it never explicitly contrasts itself with those siblings.

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 gives no when-to-use guidance, no prerequisites, and no pointer to alternatives such as drive_list_folder for browsing a known folder or drive_get_file_metadata for a known id. The agent must infer the selection from the name alone.

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