List a Drive folder

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

With no annotations provided, the description carries the burden of behavioral disclosure. It adds the non-recursive behavior ('directly inside') and the fallback to My Drive root, which are important behavioral traits beyond a simple 'list' action. It does not describe return format or pagination, but for a listing tool this is acceptable.

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?

A single, tightly worded sentence with no filler. It front-loads the core action and resource, then adds scope and defaults. Every clause earns its place.

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 list tool with no output schema, the description adequately covers purpose, scope, and default behavior. The absence of an output schema means return values need not be documented. The low complexity and clear parameter descriptions make it complete enough for an agent to use correctly.

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 100%, so the schema already documents each parameter fully. The description adds 'by URL or id' which mirrors the schema's folder parameter description, and the default root is also present in the schema. No new meaning is added beyond the schema, so baseline 3 is appropriate.

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 action ('List'), the resource ('Drive folder'), and the exact scope ('files and subfolders directly inside'), which distinguishes it from search_drive (which searches) and other sibling tools. The URL/ID input and default to My Drive root are also explicit.

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 gives clear context on when to use the tool: to list the immediate contents of a Drive folder, with a fallback to My Drive root. It does not explicitly mention alternatives or when-not-to-use, but the 'directly inside' qualifier and default behavior provide practical usage guidance.

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