outlook_save_attachment

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

No annotations are provided, so the description carries the full behavioral disclosure burden. It says what the tool does at a high level, but does not disclose permission requirements, whether existing files are overwritten, where the folder is specified, or what happens on failure. For a write/save operation with zero annotation coverage, this is a significant 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 description is a single short sentence that is front-loaded with the tool's action and target. There is no redundant or filler language. It is appropriately sized for the amount of information provided.

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 zero parameters, no annotations, and no output schema, the description is not complete enough to safely invoke the tool. It does not explain how the tool identifies the Outlook email, which folder is used, or whether it saves all attachments or a selected one. Additional context is needed for an agent to call it correctly.

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 contains zero parameters, and the scoring rules set a baseline of 4 for parameter semantics when there are no parameters. The description adds no parameter details, but there are none to document in the schema. The score reflects the zero-parameter baseline rather than any added semantic value.

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 states a specific verb ('Saves') and resource ('attachments from an Outlook email to a folder'), making the tool's basic action clear. However, it does not distinguish this tool from the sibling 'save_attachment' or clarify what makes this Outlook-specific version different. A 4 is appropriate: clear purpose without sibling differentiation.

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 gives no guidance on when to use this tool versus alternatives such as 'save_attachment' or other Outlook tools. It also does not state prerequisites, like whether the email must be selected or opened first. There is no when-to-use or when-not-to-use information.

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