25 tools with basic schemas and descriptions, but significant quality gaps. All tools have descriptions (10-50 chars, mostly generic), and input schemas are present with type definitions. However, descriptions lack LLM-optimized guidance on WHEN to use each tool, dependencies between tools, and error recovery paths. Many parameters lack constraints (enums, ranges). Output schemas are not documented. No tool annotations (readOnlyHint/destructiveHint). Composition issues: manage_events, manage_slides, manage_tasks use action enums that should be separate tools. Parameter naming inconsistencies (e.g., 'account' optional everywhere but never explained). No pagination guidance despite list tools. Error handling absent from visible code.

• Split manage_* tools into separate verbs: create_event, update_event, delete_event, list_events instead of manage_events with action enum. Repeat for calendars, slides, spreadsheets, tasks, labels. This aligns with pattern:tool single-responsibility and improves LLM tool selection.
• Expand all descriptions to 80-150 chars with LLM-optimized guidance: WHAT (one sentence), WHEN (when to use vs similar tools), PREREQUISITES (e.g., 'Requires calendar_id from list_calendars'), and ERROR RECOVERY (e.g., 'If not found, try search_*'). Example: 'Create a new calendar event. Use this after list_calendars to get calendar_id. Returns event_id for add_comment_to_event. If time conflict, check_availability first.'
• Document output schemas for all tools. Add a 'Returns' section to each tool description or create a separate schema registry. Specify: field names, types, and which fields are IDs needed by downstream tools. E.g., search_gmail_messages returns [{message_id, from, subject, snippet, date}] so LLM knows message_id chains to read_gmail_message.
• Add JSON Schema constraints: enums for action/role/type params, minLength/maxLength for strings, minimum/maximum for numeric limits. E.g., max_results: {type: integer, minimum: 1, maximum: 100}. Replace free-form 'account' with enum of known profiles or make it optional with clear default.
• Add tool annotations to all definitions: readOnlyHint=true for search_*, read_*, list_*, get_*, check_*; destructiveHint=true for delete_*, remove_*; idempotentHint=true for create_* with idempotency keys. This guides LLM retry logic and safety reasoning.