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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds that results are paginated, that navigation/sidebar data is returned, and that folder IDs are mailbox-scoped, which is useful but modest extra behavioral context.

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?

Three short sentences, front-loaded with the core action, and each sentence adds a distinct fact (pagination, folder source, account source). No filler, though the middle sentence mixes usage and parameter notes slightly.

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 read-only browsing tool with no output schema, the description covers pagination, result composition (threads plus navigation), and required ID provenance. It omits detail on how pageToken is obtained, but annotations and schema cover enough that this is a minor gap.

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 25%, so the description carries real weight: it explains that query uses the provider's search syntax and that emailAccountId should come from list_email_accounts, neither of which the schema documents. Folder meaning is largely already in the schema, so it stops short of a 5.

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 gives a specific verb and resource ("List paginated mailbox threads and sidebar navigation") and scopes it to browsing system views or provider folders, which separates it from read_mail/read_thread. It does not explicitly name the sibling search_inbox it overlaps with, so it falls short of a 5.

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?

"Browse a system view or a provider label/folder ID returned in navigation" gives implied usage context, and "Account ID comes from list_email_accounts" names a prerequisite source. However, it never says when to prefer this over search_inbox, which is the closest sibling, leaving the main routing decision to inference.

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