rename_folder

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

Annotations already indicate this is a non-readonly, non-destructive operation. The description adds meaningful context: emails inside are unaffected, system folders are restricted, and the folder hierarchy remains unchanged. This goes beyond what annotations provide and clarifies user expectations.

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 compact, front-loaded with the core purpose, and uses a clear Args section for parameters. Every sentence contributes (purpose, behavioral note, system folder restriction, param constraints) with no redundancy or fluff.

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 simple rename tool with two parameters and an output schema, the description covers purpose, constraints, system folder exclusions, and parameter semantics. Nothing critical is missing; the output schema handles return value details.

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?

With 0% schema description coverage, the description fully compensates by explaining both parameters: 'folder' (target folder name or full path with example) and 'new_name' (no '/' because hierarchy doesn't change). This adds critical meaning beyond the bare schema types.

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 verb and resource: 'フォルダの名前を変える' (change the name of a folder). It distinguishes from sibling tools like move_folder by noting '中身のメールは動かない' (emails inside don't move) and '階層は変わらない' (hierarchy doesn't change), making the rename-only scope unmistakable.

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?

Provides clear when-not guidance: system folders like Inbox/Spam cannot be changed, and the hierarchy isn't altered, which implies using a move tool for path changes. However, it doesn't explicitly name alternatives like move_folder, so it's not a full 5.

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