List Mail Folders

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It adds important context by noting a required permission ('delegated Mail.Read') and clarifying the user scope. The 'List' verb implies a read-only operation, which is helpful, though it does not mention pagination or return details.

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 main description is concise and front-loaded with the core action and resource. The Chinese intent section adds length but serves multilingual users, and the permission note is useful. Overall it is efficient without unnecessary fluff.

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 no output schema and a single optional parameter, the description covers purpose, a use case, and a permission requirement. However, it does not clarify the hierarchy (top-level vs. all folders) relative to sibling tools, leaving 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 schema already provides complete descriptions for the single parameter 'top' (coverage 100%). The description adds no parameter-specific details, so the baseline of 3 is appropriate; the schema carries the weight here.

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 a specific action ('List mailbox folders') with a defined resource scope ('for the signed-in user'). It is distinct from siblings like 'mail_list_child_folders' by implying top-level folders, though it does not explicitly differentiate itself.

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?

Provides a clear usage scenario: 'Use this to choose a destination when moving messages.' This helps the agent understand a primary use case, but it lacks explicit guidance on when not to use it or alternatives.

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