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

Annotations already cover the safety profile (readOnlyHint, destructiveHint, openWorldHint). The description adds genuine behavioral context: results are scoped to folders you can access and may be fewer than the page size. It does not cover return format or pagination handling, but adds real value beyond annotations.

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, zero waste, purpose front-loaded and the access-scoping caveat following. Every sentence 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 2-param read tool with annotations and no output schema, the description is largely sufficient. The mention of 'page size' with no corresponding pagination parameter is slightly confusing, but nothing critical to correct invocation is missing.

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 50%: mailbox is fully documented in-schema (with a list_authorized_mailboxes reference), while query has no schema description. The description partially compensates by explaining query matches item names, but gives no syntax or matching behavior detail, so baseline 3 fits.

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 ('Search one account's Google Drive for files/folders') plus the matching mechanism ('name matches a text query'). This implicitly distinguishes it from list_gdrive_items, but no sibling alternative is named explicitly.

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?

Usage is implied by the name-match criterion, but there is no explicit when-to-use/when-not guidance and no routing to alternatives like list_gdrive_items. The agent must infer the difference between searching and listing.

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