move_folder

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

With no annotations provided, the description carries the full burden of disclosing behavior. It states that the operation relocates the folder and all its contents, returns a success confirmation, and returns an error if either ID does not exist. This covers the main behavioral aspects, though it does not mention reversibility or permission requirements.

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 four sentences, each providing essential information: purpose, effect, return/error behavior, and a usage hint. It is front-loaded and contains no filler or redundant phrasing.

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?

Despite having no output schema and no annotations, the description is complete for a simple move tool. It covers the action, the scope (all contents), the success/error responses, and how to obtain necessary IDs. Nothing critical is missing for an agent to invoke the tool 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 schema already provides 100% coverage with descriptions for both parameters, including the example 'from list_folders'. The description adds little beyond this, mainly reinforcing the hint to use list_folders. It does not clarify additional formatting or relationship details beyond what the schema states.

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 action: 'Move a mail folder under a different parent folder in Outlook.' It clearly distinguishes this from sibling tools like rename_folder (which changes name) and delete_folder, and further elaborates 'Relocates the folder and all its contents to the new parent.'

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 a clear context: moving a folder to a different parent. It also provides a practical instruction: 'Use list_folders to find folder IDs.' However, it does not explicitly state when not to use this tool or compare it directly to alternatives like rename_folder.

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