driveactivity query activity

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

Annotations already declare readOnly, idempotent, open-world and non-destructive, so the safety bar is covered. The description adds real behavior beyond that: results arrive newest first, the filter uses Drive Activity syntax, and consolidate=true groups related actions. It omits pagination behavior for page_token/max_results, which keeps it from a 5.

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?

Three short blocks, front-loaded with purpose and scope, then filter syntax, then the consolidate flag. The inline example is long but earns its place by demonstrating the syntax an agent cannot infer from a bare string parameter.

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?

An output schema exists, so return values need not be described. However, for a paged query endpoint the absence of any statement about pagination, ordering across pages, or result limits leaves a meaningful operational gap for an agent that must call it repeatedly.

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 carry parameter meaning. It does well for filter (syntax plus a concrete example), item_id, folder_id and consolidate, but page_token and max_results (default 25) get no guidance at all, leaving a pagination gap in a query tool.

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 and resource ('Query Drive activity') plus the exact three scoping modes keyed to parameter names (item_id, folder_id, neither). An agent can distinguish this from drive_search_files or drive_get_file immediately, since this returns activity history rather than file content.

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?

Explicitly tells the agent which parameter selects which scope, which is the primary selection decision for this tool. It does not name alternative sibling tools or state when-not to use activity history versus a file listing, so it falls short of a 5.

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