List mail folders

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

The description implicitly indicates a read-only operation via 'list', but lacks an explicit statement about no side effects or modifications. Since no annotations are provided, the description carries full burden, and this is a minor omission.

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 a single, concise sentence that conveys the essential information without redundancy.

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?

While the description mentions IDs and item counts, it does not specify the exact return format (e.g., array, object) or potential errors. Given the absence of an output schema, a bit more detail on the return structure would be helpful, but the current level is adequate for a simple list operation.

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?

There are no parameters, so the description correctly omits any parameter details. The schema is empty, and no additional explanation is needed.

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 top-level mail folders with IDs and counts, and it distinguishes itself from sibling tools by focusing on folder enumeration rather than message operations.

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?

It explicitly instructs to use the returned folder ID with list_messages or search_messages, providing clear when-to-use and how to chain with other tools.

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