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

With no annotations, the description carries the full transparency burden. It discloses an important behavioral trait: items outside accessible folders are not returned, and page size may not be reached due to folder rules. It does not explicitly state that the operation is read-only, but 'search' strongly implies no mutation.

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 concise sentences with no filler. The core function is front-loaded, and the access-filter caveat is placed second as important but secondary context.

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?

The description is strong for a simple search tool, covering the query scope, mailbox context, and filtering behavior. There is no output schema and no explicit return-format mention, but the description's access-filter note already implies pagination and result-count behavior.

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 only 50%, but the description directly defines the query parameter as matching files/folders by name. The mailbox parameter already has a detailed schema description. This adds meaningful semantics beyond the bare 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 uses a specific verb and resource: searching one account's Google Drive for files/folders by name. It clearly distinguishes this from listing or managing Drive items and from search tools targeting other providers.

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 makes it clear this is the correct tool when the agent needs to find files/folders by name in a specific mailbox/account. It also warns that access restrictions can reduce result counts, which is relevant context for interpretation. It does not explicitly contrast with list_gdrive_items or other search siblings, but the text-query intent is clearly implied.

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