Two tools with minimal definitions. lookup_customer has a reasonable description (27 chars, below 34-char p10 baseline) and a properly typed input schema with two parameters. always_fails has a trivial description (13 chars, well below 20-char threshold) and a single parameter. Neither tool has documented output schemas. Parameter descriptions are present but terse. No error handling guidance, no recovery paths, no idempotency hints. Tool names lack clarity on what 'lookup' returns or why 'always_fails' exists. This appears to be a conformance fixture, not a production MCP server.

• Expand lookup_customer description to 50-150 chars: 'Retrieve customer details by ID. Returns name, email, account status, and contact info. Use include_secret_notes=true only if authorized to view internal notes.'
• Document output schema for lookup_customer: {customer_id, name, email, account_status, created_at, secret_notes?}. Specify which fields are always present vs. conditional.
• Replace always_fails with a meaningful tool or remove it. If testing error paths, add a tool like 'simulate_error' with a description explaining it's for testing resilience.
• Add error handling to lookup_customer description: 'Returns 404 if customer not found. Try search_customers() with a partial name if you only have a first/last name.'
• Clarify the include_secret_notes parameter: 'Boolean flag (default: false). When true, includes internal notes field. Requires admin permission, will fail silently if user lacks access.'