mcpguard is a security scanner tool, not a production MCP server. The two tools in tests/fixtures/mock_server.go are test fixtures, not the actual server implementation. Tool definitions lack parameter descriptions entirely. 'hello' has a basic schema but no parameter docs. 'trigger_rugpull' has an empty input schema with no description of what parameters it accepts. Descriptions are minimal (10-20 chars). No output schemas documented. No error handling guidance. This is a test harness, not a real MCP server.

• Add comprehensive parameter descriptions to all tool inputs. For 'hello', document: 'name (string, required): The person's name to greet. Accepts any non-empty string.'
• Define output schemas explicitly. Document that 'hello' returns {type: 'text', text: string} and what fields clients should expect.
• Expand tool descriptions to 50-200 characters following pattern:tool-description. Include WHAT it does, WHEN to use it, and any prerequisites.
• For 'trigger_rugpull', clarify the purpose and side effects. Is this a test-only tool? Document that it mutates the schema and what the mutation entails.
• Add error handling guidance. Document what errors can occur (e.g., invalid name format) and how to recover.