m365_list_email_folders

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

No annotations exist, so the description carries the full behavioral burden, and it delivers almost nothing: it does not say whether this is read-only, whether it requires a connected account, or how many levels of folders are returned. The truncated clause about the 'Exchange serv...' hints at a return shape but is cut off before conveying anything usable.

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 single sentence is short and front-loads the trigger condition, which is good. But it is literally incomplete text that stops mid-word, so the brevity comes from truncation rather than discipline.

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 annotations and no output schema, the description is the only place an agent can learn what this returns. It never says what a folder record looks like, whether hierarchy or counts are included, or what happens if no M365 account is connected.

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. No parameter guidance is needed and none is missing.

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 (mail folders) and the account type (Microsoft 365 / Outlook), so the agent can infer a folder-listing operation. However, it never states the verb explicitly and the sentence is truncated mid-word, leaving the actual scope ('as the Exchange serv...') undefined.

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?

'Use this when the user wants the mail folders of their Microsoft 365 / Outlook account' is an implied when-to-use trigger, which is better than nothing. There is no mention of alternatives such as list_email_folders or m365_create_email_folder, and no exclusion criteria.

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