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 useful behavior beyond that: newest-first ordering, pagination, and the exact shape of returned summaries (sender, subject, date, snippet, uid, labels), which tells the agent what a result row contains.

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 compact sentences: the primary list behavior and the returned fields are front-loaded, with the draft-folder tip appended. No sentence is wasted or redundant.

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?

With no output schema, the description compensates by enumerating the returned fields, and pagination is stated in prose while its parameters are fully specified in the schema. It is close to complete; only the relationship to search tools and any result-count/paging metadata behavior are unaddressed.

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 description coverage is 100%, so every parameter is already documented, including defaults and the 1-100 limit range. The description only echoes the folder concept ("Drafts") without adding format or constraint detail beyond the schema, so the baseline 3 applies.

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 (List) and resource (message summaries) and enumerates the returned fields, plus ordering and pagination behavior. It does not name or contrast with the closest sibling, search_messages, so an agent must infer the list-vs-search boundary.

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?

One concrete usage hint is given (folder "Drafts" for saved drafts), but there is no guidance on when to choose this over search_messages or search_all_mailboxes, nor any stated prerequisite such as a needed mailbox argument. Usage is only implied for the common case.

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