m365_save_attachment

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

No annotations are supplied, so the description carries the full burden. It says the tool writes attachments to 'a folder' but never states which folder, whether an existing file is overwritten, what naming scheme is used, whether authentication or a default account is required, or what the tool returns on success or partial failure. For a filesystem-writing operation this is a substantial gap.

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 text is short and front-loads the verb and resource, which is good. However, it terminates mid-word, so it is under-specified rather than concise — the trimming removed exactly the detail an agent needs.

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, no output schema, and an empty parameter schema, the description is the only source of behavioral information, and it does not cover destination folder, overwrite semantics, return value, or error behavior. The truncation makes it impossible to know the full intended contract.

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 declares zero parameters, so the baseline would be high, but the description references an email and an attachment_id that do not appear in the schema, which is confusing rather than clarifying. It does add the useful semantic that omitting attachment_id saves all attachments, but the sentence explaining the id source is cut off before it can be used.

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 gives a specific verb and resource: saves the attachments of a Microsoft 365 email to a folder, and it distinguishes itself from provider siblings (outlook_save_attachment, whatsapp_save_media) by naming Microsoft 365 explicitly. The core purpose is understandable, but the sentence is truncated mid-clause ("the ids m..."), leaving the scope statement unfinished.

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?

There is no guidance on when to choose this over the sibling save_attachment or outlook_save_attachment tools, and no mention of prerequisites such as a connected Microsoft 365 account. The only usage signal is the implicit 'all of them, or one by attachment_id' choice, which is a parameter behavior rather than a when-to-use rule.

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