Workspace.Drive.List Files

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

No annotations are provided, so the description carries the entire burden. It implies a read-only listing scoped to accessible files, but says nothing about pagination behavior, result limits, ordering, permission/scope requirements, or what happens if the query is malformed. For an unannotated list tool this leaves major behavioral gaps.

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?

One tight sentence with the scope constraint placed where it matters; nothing is padded. It is efficient, though efficiency here partly reflects under-specification rather than discipline.

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-value shape need not be described. But for a list tool with a single opaque filter parameter and no annotations, the definition should still cover pagination and filter syntax; those omissions make it only minimally adequate.

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% and the sole parameter 'query' has only a default of empty string, so the description must explain it. 'Optional files.list query' hints that it takes a Drive v3 q-style filter expression but never states the syntax, whether the field is prefixed with 'name =' style clauses, or that omission returns everything — so the agent is left guessing.

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 (list Drive files) plus the scope constraint 'the authenticated user can access'. The only blur is the parenthetical 'optional files.list query', which gestures at the underlying API rather than adding clarity, but an agent can still tell what the tool returns.

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?

No statement of when to use this versus anything else, no prerequisites, no exclusions. The description never says what the sibling tools cover or when a different listing call would be appropriate, so the agent must infer selection from the name alone.

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