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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=false, and the description usefully adds scope: only the display name changes, so existing identifiers and presumably version content are untouched. It also discloses validation behavior (empty/whitespace-only names are rejected), which is genuinely extra context beyond the annotations, though it says nothing about permissions or idempotency.

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?

Three tight sentences with zero filler, front-loading the core action and immediately following with the scope constraint and accepted input forms. Every sentence carries information an agent needs.

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 described, and the annotations cover the safety profile. The description covers identity semantics (label vs `v<N>`) and validation, but omits whether a permission level is required and whether the name must be unique, which would round out a mutation 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 100%, so all three parameters (name, projectId, versionId) are already documented in the schema, including the UUID/`v<N>` shorthand for versionId and the non-empty requirement for name. The description largely restates those same facts, so baseline 3 applies.

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?

Specific verb (rename) plus precise resource (a saved version's human-readable label), with a parenthetical clarifying exactly what the label is ('what the user sees in the picker'). It also explicitly distinguishes this from changing the `v<N>` identifier, which cleanly separates it from rename_layer, rename_group, rename_project and rename_workspace siblings.

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 clear context for when this tool is appropriate (changing the display label only) and states what it does NOT do (the partner-facing `v<N>` identifier is unaffected). It doesn't name an explicit alternative tool or state prerequisites/permissions, so it falls short of the full when/when-not/alternatives bar.

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