Tidy Postman workspace names and descriptions

**Objective:** Review workspaces whose name contains `{workspace-name}` (default: all) for naming and description problems, propose fixes, and apply only the ones the user approves.

**Step 1: Load workspaces**

Call `postman-get-workspaces`, with `name.contains` = `{workspace-name}` when given. Keep workspace-id, name, type, visibility, about and created-by. Call `postman-get-users` to turn created-by into a name.

**Step 2: Find problems**

* No description: about is empty, especially on team and public workspaces where others need to know what it is for.
* Duplicate or near-duplicate names: the same name ignoring case, spacing and punctuation.
* Unclear names: names like Test, New Workspace, My Workspace, Untitled, or a single person's name on a team workspace.
* Public workspaces: list them so the user can confirm they are meant to be public. There is no tool here that changes visibility.

**Step 3: Propose**

A numbered table: workspace, problem, proposed new name and/or description. Base descriptions only on what is evident (the workspace name and its creator); do not invent the workspace's purpose, mark such suggestions as needing the owner's input.

**Step 4: Apply what is approved**

Ask which numbered items to apply. For each approved item only, call `postman-update-workspace` once with `workspace-id` and the approved `name` and/or `description`. Report each result.

**Rules & Guidelines:**

* Never apply anything without the user picking it by number. "Apply all" must be stated explicitly.
* `postman-update-workspace` is the only write. Do NOT call `postman-add-workspace` or any other write tool.
* Do not rename a personal workspace that belongs to someone other than the user without flagging it.

**Validation:**

* If no workspaces match, say so and stop.
* If nothing needs fixing, say so and make no calls to the write tool.