Three tools with severely deficient schemas and descriptions. gdrive_connector and GPT5-gdrive-fixer have vague, legacy-focused descriptions (under 200 chars but lacking actionable context). GPT5-web-search is minimal. Tool names are non-standard (gdrive_connector lacks verb prefix; GPT5-* prefix is non-idiomatic). No output schemas documented. No error handling guidance. No parameter constraints (enums, ranges). Descriptions do not explain WHEN to use each tool or what happens on failure.

• Rename tools to verb_noun format: gdrive_connector → execute_gdrive_code, GPT5-gdrive-fixer → repair_gdrive_code, GPT5-web-search → search_web. Use underscores, not hyphens.
• Add 50 - 150 character descriptions for each tool explaining WHAT it does and WHEN to use it. Example: 'execute_gdrive_code: Runs a self-contained JavaScript snippet against the Google Drive API. Use this to create, read, or modify files in Google Drive. Returns success/failure and any API response data.'
• Add descriptions to every parameter. Example for self_contained_javascript_gdrive_code_snippet: 'A complete, executable JavaScript code snippet using the Google Drive API. Must include all imports and error handling. Will be executed in a sandboxed environment.'
• Document output schemas for each tool. Specify what fields are returned on success (e.g., execution_result, error_message, status_code) and their types.
• Add error handling guidance to descriptions. Example: 'On failure, returns error_message with details. If code syntax is invalid, call repair_gdrive_code with the error message. If API credentials are missing, contact the administrator.'