outlook_move_email

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It does not state whether the operation is reversible, what permissions are required, whether the destination folder must already exist, or what happens on conflicts. For a mutation tool 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 efficient sentence with no wasted words, and the core action is front-loaded. It is appropriately sized, though its brevity contributes to the gaps noted elsewhere.

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?

For a mutation operation, the definition is incomplete: there are no annotations, no output schema, and no parameters in the schema to identify the email or destination folder. The description does not compensate for these omissions, leaving an agent unable to invoke the tool correctly from the definition alone.

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 has zero parameters, and the rule baseline for zero-parameter tools is 4. The description does not need to document parameters that do not exist, though it also fails to explain why a move operation has no parameters.

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 ('Moves'), resource ('Outlook email'), and destination ('to a different folder'), so the core action is clear. However, it does not distinguish itself from the sibling tool 'move_email', which likely performs the same operation, leaving the agent unsure which one to choose.

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 use this tool versus alternatives such as 'move_email', nor any prerequisites or exclusions. The agent receives no routing information despite a dense sibling toolset.

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