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

Annotations already declare destructiveHint=true and idempotentHint=false; the description adds genuine context by enumerating what is NOT affected, which is exactly the reassurance an agent needs before invoking a hint-flagged destructive mutation. It stops short of stating permission requirements or error behavior, but it materially supplements 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?

Two short sentences, action front-loaded, followed by the scope disclaimer. No filler.

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?

An output schema exists, so return values need not be explained, and the mutation's side-effect scope is covered. However, with three undocumented required parameters and no prerequisites or failure modes mentioned, the definition is incomplete for a destructive write tool.

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% across three required parameters, so the description carries the burden of explaining them — yet it adds nothing about folderId, projectId, or the name constraints (1-60 chars). The phrase 'its ID' only loosely gestures at folderId.

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?

States a specific verb ('renames') and resource ('screenshot folder'), and the second sentence delimits the exact scope of the change (ID, locale binding, storage paths, saved designs untouched). This clearly separates it from siblings like create_asset_folder, delete_asset_folder, and set_asset_folder_locale.

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 'unchanged' clause implies this is a pure metadata-label change, which helps an agent decide when it is appropriate, but there is no explicit when-to-use/when-not guidance and no named alternative for tasks like relabeling locale or moving contents.

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