List My Mail

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

With no annotations provided, the description carries the full burden. It discloses the required permission (delegated Mail.Read) and the scope (signed-in user mailbox), but does not specify return format, pagination, or explicitly confirm read-only behavior. The term 'recent' is vague.

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?

The description is concise and front-loaded, with three short sentences covering purpose, capabilities, and permissions. The Chinese intent list adds length but is useful for multilingual support. No unnecessary fluff is present.

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 simple list tool with two well-documented parameters, the description provides adequate context: what it does, query options, and permissions. It lacks an explicit return-value description, but 'list messages' implies a list. The ambiguity of 'recent' 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?

The input schema already provides full descriptions for both parameters (top and unreadOnly), achieving 100% coverage. The description adds minimal value by mapping 'recent' to top and 'unread' to unreadOnly, but this is not beyond what the schema states.

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 clearly states the tool lists recent messages from the signed-in user's mailbox, using a specific verb and resource. It distinguishes itself from sibling tools like mail_list_folder_messages (folder-specific) and mail_search_messages (search-based) by emphasizing recent/unread queries.

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 explicitly mentions supporting recent mail and unread mail queries, giving clear context on when to use the tool. However, it does not mention alternatives or exclusions, such as pointing users to search for keyword queries or folder listing for specific folders.

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