`tool-list` skill name and description lack Unity-MCP context, causing ambiguity in multi-MCP environments

[dogukankse]

The tool-list tool is registered with a generic name and description:

public const string ToolListId = "tool-list";

[Description("List all available MCP tools. Optionally filter by regex across tool names, descriptions, and arguments.")]

When the generated skill is loaded by Claude Code (or any MCP-aware AI client), both the identifier and the description are completely context-free. In a setup with multiple MCP servers, this creates two problems:

1. Name collision risk — another MCP server could register a tool named tool-list, causing a conflict.
2. Poor AI routing — the AI has no signal that this tool is scoped to Unity Editor. "List all available MCP tools" reads as a universal tool, not a Unity-specific one.

Expected behavior

The tool name and description should make the Unity-MCP scope explicit:

public const string ToolListId = "unity-tool-list";
// or namespaced: "unity-mcp/tool-list"

[Description("List all available Unity-MCP tools registered in the connected Unity Editor instance. Optionally filter by regex across tool names, descriptions, and arguments.")]

Impact

This affects all generated skills — tool-list is the entry point tool that AI agents use to discover other Unity-MCP tools. If the AI misroutes or misidentifies this tool, the entire MCP session degrades.

Suggested fix

• Rename ToolListId to unity-tool-list (or prefix all tool IDs consistently)
• Update the [Description] to include "Unity Editor" / "Unity-MCP" context