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

With no annotations, the description carries the burden. It discloses that only items in accessible folders are returned, which is useful. However, it does not mention whether the result is paginated, whether it includes metadata like file sizes or modified dates, or whether it is a read-only operation (though 'list' implies it).

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?

Two sentences, front-loaded with the core action and default behavior, then a clarifying scope note. No wasted words.

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 2 parameters and no output schema, the description is mostly adequate. However, it lacks guidance on pagination, sorting, or what fields are returned, which an agent might need to correctly interpret results. The sibling list is large but the description's scope note helps differentiate from search_gdrive_items.

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 coverage is 100%, so the schema already documents both parameters. The description adds the default behavior for itemId (root) and clarifies mailbox scope, but does not add significant new meaning beyond the schema.

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 lists files and folders inside a Google Drive folder, defaulting to My Drive's root, for one account. It distinguishes itself from search_gdrive_items by focusing on listing within a folder rather than searching, though it doesn't explicitly name the sibling.

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 usage: call it to list items in a folder, with itemId optional to target a specific folder. It does not explicitly state when to prefer this over search_gdrive_items or list_onedrive_items, nor does it mention exclusions like pagination or permission requirements.

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