drive_watch_changes

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

No annotations are provided, and the description fails to disclose behavioral traits such as the need for authentication, channel expiration, or that this creates a long-lived subscription that should be stopped using 'drive_stop_channel'. The description is too brief to cover these important aspects.

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 that is concise and front-loaded with the core purpose. However, it could benefit from additional context without being verbose.

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 of push notification subscriptions, the absence of annotations and output schema, and the presence of sibling tools like 'drive_stop_channel', the description is incomplete. It does not cover the lifecycle of the channel or how to manage it, leaving gaps for the agent.

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?

Input schema coverage is 100%, so the schema already documents all parameters. The description adds no additional meaning beyond what is in the schema, e.g., it does not explain that 'pageToken' is obtained from 'getStartPageToken' or that 'channelAddress' is a callback URL.

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 subscribes to changes in Google Drive via push notifications, specifying verb and resource. However, it does not differentiate from the sibling tool 'drive_watch_file' which watches a specific file, leaving ambiguity about scope.

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 guidance on when to use this tool vs alternatives like 'drive_list_changes' or 'drive_stop_channel'. It does not mention prerequisites like obtaining a start token from 'drive_get_changes_start_token'.

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