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

The annotations already declare destructiveHint=true and readOnlyHint=false, so the description does not need to restate that this is a mutation. It adds useful context by saying 'Free' and restricting the operation to the user's own folders, though it does not explain rename side effects or constraints.

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 short sentences with no wasted text. The ownership restriction and ID source are front-loaded and directly useful.

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 two-parameter mutation with annotations covering the safety profile, the description provides enough context to invoke it correctly. It could be improved by noting that name is the new folder name, but no output schema means return-value details are less critical.

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 0%, so the description must carry the burden. It clarifies where folderId comes from via list_my_folders, but it does not describe the name parameter beyond the verb 'rename,' nor does it document any naming constraints or validations.

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 and resource: 'Rename one of your folders.' It also identifies the folder by ID sourced from list_my_folders, clearly distinguishing this from sibling tools such as create_folder and delete_my_folder.

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?

It gives clear usage context: the folder must be one of the user's own folders, and the ID comes from list_my_folders. It does not explicitly compare against create_folder or delete_my_folder, but the operation is unambiguous for an agent.

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