docs(router): document omit_operation_prefix config for MCP tool names

Add documentation for the new omit_operation_prefix configuration option
that allows cleaner MCP tool names without the execute_operation_ prefix.

Related: wundergraph/cosmo#2441

Author: shamashel

docs/router/mcp.mdx

@@ -216,6 +216,7 @@ mcp:
   exclude_mutations: true
   enable_arbitrary_operations: false
   expose_schema: false
+  omit_operation_prefix: false  # When true: GetUser → get_user (no execute_operation_ prefix)
 
 # Configure storage providers
 storage_providers:
@@ -237,6 +238,7 @@ storage_providers:
 | `exclude_mutations`           | Whether to exclude mutation operations from being exposed                                                                                                | `false`          |
 | `enable_arbitrary_operations` | Whether to allow arbitrary GraphQL operations to be executed. <Warning>Security risk: Should only be enabled in secure, internal environments.</Warning> | `false`          |
 | `expose_schema`               | Whether to expose the full GraphQL schema. <Warning>Security risk: Should only be enabled in secure, internal environments.</Warning>                    | `false`          |
+| `omit_operation_prefix`       | When true, MCP tool names are generated without the `execute_operation_` prefix (e.g., `GetUser` → `get_user` instead of `execute_operation_get_user`). Can also be set via `MCP_OMIT_OPERATION_PREFIX` environment variable. | `false`          |
 
 ## Session Handling
 
@@ -375,6 +377,25 @@ The MCP server converts each operation into a corresponding tool:
 
 Operations are converted to snake_case for tool naming consistency.
 
+#### Omitting the Operation Prefix
+
+By default, all operation tools include the `execute_operation_` prefix. If you prefer shorter, cleaner tool names, enable the `omit_operation_prefix` configuration option:
+
+```yaml
+mcp:
+  enabled: true
+  omit_operation_prefix: true
+```
+
+With this option enabled:
+
+- Operation name: `GetUsers` → Tool name: `get_users`
+- Operation name: `CreateUser` → Tool name: `create_user`
+
+<Warning>
+Enabling this option changes all tool names and may break existing integrations that rely on the `execute_operation_` prefix. Only enable this for new deployments or when you can update all dependent systems.
+</Warning>
+
 ### Best Practices
 
 1. **Meaningful names**: Give operations clear, action-oriented names that describe what they do.