List Drive files

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

With no annotations, the description carries the burden of behavioral disclosure. It adds useful details like 'newest first' and 'optional query,' but it does not disclose return format, scope (e.g., all files vs. folders), or authentication requirements. This is a minimal but not misleading disclosure.

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 a single, front-loaded sentence that efficiently conveys the tool's purpose and key behavior. There is no redundant information or 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?

The tool is simple with 3 parameters all described in the schema, but the lack of output schema and annotations means the description should clarify return values and scope. It does not mention what is returned or any limitations, making it adequate but not fully complete.

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 100%, so the baseline is 3. The description does not add meaning beyond the schema; it merely says 'optional query,' which is already indicated by the schema. However, it also mentions 'newest first,' which relates to sorting behavior but not directly to 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 'List files in Drive, newest first, with an optional query' clearly states the action (list), the resource (Drive files), and key modifiers (newest first, optional query). This distinguishes it from sibling tools like google_drive_get (single file), google_drive_upload, and google_drive_delete.

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 listing Drive files, but it does not explicitly state when to use this tool versus alternatives such as google_drive_get or other list tools. There is no mention of exclusions or differentiators beyond the basic purpose, so guidance is only implied.

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