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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds genuinely useful behavior beyond that — system folders (trash, spam, sent, drafts) are omitted and results reflect the last sync rather than live state — but it doesn't say how fresh syncs happen or whether results are paginated or ordered. Good additive context, not rich enough for a 4-5.

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 short sentences, zero waste, with the mailbox scope front-loaded and the exclusion set following. Every clause carries information an agent would otherwise have to guess.

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?

An output schema exists, so return-value structure needn't be spelled out, and with no parameters there is little surface area to cover. The one remaining gap is the 'last synced' notion — an agent isn't told whether results can be stale or how to force a refresh.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The implicit filter is fixed and described in prose rather than exposed as an argument.

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 names the resource precisely ('the folders of each connected mailbox') and adds a scope qualifier ('as last synced'), which lets an agent distinguish it from email-listing siblings like search_emails or list_replies_to_validate. It leans on the name/title for the verb 'list', so it isn't fully self-contained, but the resource and domain are unambiguous.

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 only implied: an agent can infer this is the discovery call to run before move_email or archive_email, but the description never states when to use it or names any alternative. There are no exclusions beyond the folder-type filter, so callers get context but no routing guidance.

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