This is a test/mock server, not a production MCP tool. All three tools are defined in test-support/mock-server.ts with minimal descriptions and incomplete schemas. 'echo' and 'leak_secret' have trivial descriptions (<20 chars). 'run_bash' description is 60 chars but marked FAKE. Input schemas are present but sparse: 'echo' has a single string param with description; 'leak_secret' has empty input {}; 'run_bash' has a command param. No output schemas documented. No error handling guidance. Tool names are acceptable (verb-noun style) but descriptions fail the 20-char minimum for two tools. This server appears designed to test the firewall's policy/audit layer, not to provide production-grade tools.

• Expand 'echo' description from 'Echo back the provided text.' to explain when to use it (e.g., 'Echoes back the provided text unchanged. Use to verify text transmission or test connectivity.').
• Add a proper description to 'leak_secret': 'Returns a fake secret string for testing secret detection policies. Does not contain real credentials.'
• Document output schemas for all tools. E.g., echo returns {"text": string}, leak_secret returns {"secret": string}, run_bash returns {"stdout": string, "stderr": string, "exit_code": number}.
• Add error handling guidance: 'If echo fails, the connection may be broken. Retry once before reporting failure.'
• Clarify that 'run_bash' is a fixture tool for testing the firewall's policy engine, not a real shell executor. Update description to: 'FIXTURE: Simulates shell command execution for testing firewall policies. Never actually executes commands.'