Save whole thread

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

No annotations are provided, so the description must carry the behavioral burden. It discloses that the tool saves messages and attachments but does not mention important behavioral traits such as read-only nature, required authentication, rate limits, or error handling. The lack of output schema further limits transparency.

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 sentence that conveys the core functionality without extraneous information. It is front-loaded with the input requirement and efficiently communicates the action and outcome.

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?

Given the tool's simplicity (2 parameters, no output schema, no annotations), the description is adequate but lacks details about output format, error handling, and permission requirements. For a comprehensive agentic use, more contextual completeness would be beneficial.

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 description only mentions 'message id' and 'attachments' indirectly, but the input schema has two parameters with no descriptions. With 0% schema coverage, the description adds minimal extra meaning beyond the parameter names. It does not explain the default value of includeAttachments or constraints on messageId.

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's purpose: saving every message in a conversation along with attachments as .eml files with manifest entries. The verb 'save' and resource 'whole thread/conversation' are specific, and it distinguishes itself from the sibling tool 'outlook_save_message' which saves a single message.

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 implies usage when users need to save an entire email thread rather than a single message, but it does not explicitly state when to use this tool versus alternatives like outlook_save_message. No usage exclusions or context signals are provided, but the instructions are clear enough for basic selection.

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