Warden's test echo server has minimal tool definitions. Tool descriptions are present but generic (10-50 chars, below the 50-200 char LLM-optimized baseline). Input schemas exist but are bare JSON Schema with no parameter-level documentation. No output schemas documented. No error handling guidance. The 'danger' tool is marked DESTRUCTIVE but has no confirmation/dry-run pattern. This is a test fixture, not production-grade tooling.

• Add parameter descriptions to all tools. E.g., 'text' → 'The string to echo back (max 1000 chars)'. 'cmd' → 'The command argument to echo (alphanumeric only, no shell metacharacters).'
• Expand tool descriptions to 50-200 chars. Explain WHAT each tool does, WHEN to use it, and what it returns. E.g., 'echo: Returns the input text unchanged. Use to test round-trip communication. Returns: {type: text, text: <input>}'
• Document output schemas in tool descriptions or as a separate schema field. E.g., 'Returns TextContent with type=text and text field containing the echoed string.'
• Add input schema constraints: 'text' should have maxLength, 'cmd' should have a pattern (e.g., ^[a-zA-Z0-9_-]+$) to prevent injection.
• For 'danger' tool: implement a confirmation pattern (dry-run or explicit approval) and document error cases (e.g., 'Invalid command format: must match [a-zA-Z0-9_-]+').