Laravel Auditor exposes 11 read-only context collection tools via a custom MCP adapter. All tools lack input parameter descriptions and most lack meaningful output schema documentation. Tool names are noun-based ('authorization', 'configuration') rather than verb-based ('get_authorization', 'describe_configuration'), making intent ambiguous. 10 of 11 tools have empty input schemas (no properties), violating the pattern:tool requirement that parameters be described. The 'routes' tool is the only exception with 4 documented filter parameters. Descriptions are present but generic (e.g., 'Authorization context collector', 34 chars, below the 50-char baseline for clarity). No error recovery guidance, no output schema documentation, and no indication of what data structure each tool returns. Tool composition is sound (each does one thing), but the interface lacks the LLM-optimization needed for reliable agent selection and parameter binding.

• Rename all tools to verb_noun format: 'get_authorization', 'describe_configuration', 'list_database_schema', 'list_dependencies', 'list_jobs_events_schedules', 'list_migrations', 'list_models', 'get_project_info', 'list_routes', 'list_subsystems', 'list_tests'. This aligns with the 90% baseline of A+ tools and makes intent unambiguous.
• Expand descriptions to 80 - 150 characters, answering: What data does this tool return? When should I call it instead of similar tools? Example: 'Get authorization policies, roles, and permissions defined in the Laravel app. Call this to understand access control before suggesting security changes.'
• Document output schemas for each tool. Add a 'returns' section to each tool's description or code comment specifying the JSON structure (e.g., 'Returns: {policies: [{name, description, actions}], roles: [{name, permissions}]}'). This enables LLMs to chain tools correctly.
• For tools with optional filters (currently only 'routes'), add parameter descriptions to all filter fields. Example: 'uri: Filter routes by URI pattern (e.g., /api/users). Supports wildcards.' Ensure all 10 other tools document any hidden filters or explain why they accept no parameters.
• Enhance error handling in AuditTool.handle() to return structured errors with recovery hints. Example: 'Error collecting context: Database connection failed. Ensure Laravel is configured and the database is accessible. Retry or check configuration tool.' This guides LLM recovery.