Critical failures across naming, descriptions, and schema visibility. Tool names lack clear action verbs (e.g., 'db_migrate_rbac', 'db_seed_rbac_defaults' are vague). Most tool descriptions in the provided spec are generic 1-2 sentence stubs (10-50 chars), far below the 194-char baseline. Schemas are partially visible in admin-tool.ts but most tools (13-30) have no visible schema definitions in source, only inferred from the spec table. The 'apiKey' parameter appears in every tool definition but should NEVER be exposed as a parameter per pattern:secret-injection. No input validation guidance, no error recovery hints, no output schema documentation visible. Composition is poor: 30 tools with overlapping concerns (e.g., multiple RBAC tools that could be consolidated). No pagination, no result limits documented.

• Remove 'apiKey' parameter from ALL tools. Move authentication to server-side environment variables (MYSQL_API_KEY) or a secure vault. Update tool schemas to remove apiKey entirely. Agents should not handle credentials.
• Expand tool descriptions to 100-200 chars. For each tool, answer: What does it do? When should the LLM call it instead of similar tools? What does it return? Example: 'create_role' → 'Create a new RBAC role with optional description. Use this before assign_role_to_user to define a new permission group. Returns role_id, name, created_at.'
• Document output schemas for all tools. Add a 'Returns' section to each tool description or create a separate schema file. Specify field names, types, and whether results are paginated. E.g., list_roles returns {roles: [{id, name, description}], total_count, next_cursor}.
• Rename 'db_*' tools to use clear action verbs: db_migrate_rbac → migrate_rbac_schema, db_seed_rbac_defaults → seed_default_roles, db_check_integrity → verify_rbac_integrity. Ensure all tool names start with a verb (get, list, create, delete, update, migrate, seed, verify).
• Add input validation and error guidance. For execute_query, document SQL injection prevention and timeout behavior. For destructive tools (delete_role, kill_query), add a confirmation step or dry-run parameter. Return actionable error messages: 'Invalid role_id: 42 not found. Available roles: admin (1), user (2), guest (3).' instead of bare error codes.