list_files

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

There are no annotations, so the description carries the behavioral disclosure burden. It clarifies that listing can be scoped by folder, filtered by MIME type, and limited by page size, and states the returned fields. However, it does not mention permissions, pagination behavior beyond page_size, sorting, or whether subfolders are included recursively.

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 concise and well-structured with a one-line purpose followed by Args and Returns sections. Every sentence contributes useful information without unnecessary elaboration.

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?

For a simple listing tool with three optional parameters and an output schema, the description is mostly complete: it explains all parameters and the shape of the result. It falls slightly short by not addressing the relationship to search_files or any behavioral caveats such as recursive listing or authentication requirements.

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 description coverage is 0%, so the description must compensate. It defines all three parameters with meaningful semantics: folder_id's 'None for all files', page_size as a maximum, and file_type as a MIME filter with an example. It lacks only minor detail such as page_size bounds or folder ID format.

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 states a specific action ('List') and resource ('files and folders in Google Drive'), which clearly identifies what the tool does. It is distinguishable from course/assignment siblings by resource, though it does not explicitly differentiate itself from the similarly scoped sibling 'search_files'.

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 provides no explicit guidance on when to use this tool versus alternatives. It does not mention 'search_files' for searching, nor does it state any exclusions or preferred conditions, leaving the agent to infer usage from the name and first line alone.

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