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

Annotations declare readOnlyHint=false, destructiveHint=false, openWorldHint=false, so the safety profile is partly covered. The description adds the return payload shape and the no-op semantics of omitting parentId, but does not address permission requirements or failure/conflict behavior for a move operation.

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?

Four tight sentences, front-loaded with the action and its constraint, then prerequisites, then the return shape. Dense but every sentence adds usable information with 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?

For a 3-parameter mutation tool with no output schema and no annotation-level detail on returns, the description supplies the return fields explicitly, the prerequisite lookup, and the parameter constraints. An agent has everything needed to call it correctly.

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 carries the full burden and does so well: it explains the required 'at least one of' constraint and the crucial parentId distinction (null = workspace root, omit = unchanged), which the schema cannot convey. Only minor details like name length limits are omitted.

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 ('Update a folder name and/or move it to a different parent'), covering both mutation modes. This cleanly distinguishes it from siblings workspaceFolder_create, workspaceFolder_delete, and workspaceFolder_list.

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 an explicit precondition ('Pass at least one of name or parentId') and names a required prerequisite call ('call workspaceFolder_list for folderId and any target parentId'). It does not name alternatives, but the operation is unambiguous enough that no sibling routing is needed.

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