drive_list_changes

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

No annotations are provided, so the description must fully disclose behavioral traits. It does not mention whether the operation is read-only, what permissions are needed, or how pagination works. The simple 'list changes' statement lacks necessary context for safe invocation.

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 sentence of 13 words, which is very concise. It front-loads the key action. However, it could be slightly more detailed without becoming verbose, such as mentioning the purpose of the page token relative to incremental changes.

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 that the tool has 5 parameters, no output schema, and no annotations, the description is insufficiently complete. It does not explain the return format, pagination behavior, or how to use the results effectively. Agents need more guidance for successful invocation.

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 input schema has 100% description coverage for all 5 parameters, so the baseline is 3. The tool description adds value by connecting 'pageToken' to the 'given page token' concept, but it does not elaborate on other parameters like spaces, pageSize, includeRemoved, or restrictToMyDrive beyond what the schema already says.

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 purpose: 'List changes to files in Google Drive since a given page token'. It specifies the verb (list), resource (changes to files), and the mechanism (page token), which distinguishes it from sibling tools like drive_list or drive_get_changes_start_token.

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 that a page token is required, hinting at the need to first call get_changes_start_token, but it does not explicitly state when to use this tool versus alternatives like drive_list or drive_watch_changes. No exclusions or conditions are provided.

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