update-mail-folder

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

Annotations already declare destructiveHint=true and readOnlyHint=false, signaling a write operation. The description adds no extra behavioral context (e.g., what happens to existing properties, whether changes are reversible). It's consistent but doesn't go beyond the annotations.

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 two sentences with no fluff. The main purpose is front-loaded, and the tip is immediately useful. It's concise and structured for quick comprehension without redundancy.

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 complex body schema with many properties, the description plus the schema covers what an agent needs: required fields are clear, and the tip provides a practical workflow. The only minor gap is not explicitly stating which properties are non-updatable (e.g., isHidden is creation-only), but that's already conveyed in the schema property descriptions.

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?

Schema description coverage is high (80%), and the parameter descriptions are rich—especially mailFolderId, which clarifies naming convention and origin. The tip further highlights displayName as a key property for renaming, adding semantic value beyond the raw schema.

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 'Update the properties of mailfolder object,' which identifies the verb and resource. The tip adds a concrete use case (renaming via displayName). However, it doesn't explicitly distinguish itself from sibling update tools like update-calendar-event or update-mail-rule, though the resource is clear.

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 tip advises using list-mail-folders to find the folder ID, which is a helpful prerequisite. It also implies this tool is for renaming or updating folder properties. However, it doesn't explicitly state when NOT to use it (e.g., use create-mail-folder for new folders, delete-mail-folder for deletion) or compare with other update tools.

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