Critical gaps across all dimensions. Tool definitions lack proper schemas, descriptions are minimal or absent, and parameter documentation is severely incomplete. Only 2 of 6 tools have descriptions exceeding 20 characters. No input schemas visible for web_search or google_search. WRITE tools (change_opportunity_stage, update_task, sync_meeting, update_account) lack error handling guidance, confirmation patterns, and permission documentation. No output schemas documented. Tool names are acceptable (verb_noun pattern) but descriptions fail to explain WHEN to use each tool or what they return.

• Add explicit JSON Schema to web_search and google_search with typed parameters. For web_search, define maxUses as {type: 'number', minimum: 1, maximum: 10, description: 'Maximum number of search queries to execute (1-10)'}.
• Write 50-150 character descriptions for each tool explaining WHAT it does and WHEN to use it. Example for google_search: 'Search the web using Google AI provider. Use when you need current information or web results. Returns ranked list of URLs and snippets.'
• Document output schemas for all tools. Example: change_opportunity_stage should return {opportunity_id, stage, updated_at, previous_stage} so agents know what fields are available.
• Add error handling guidance to WRITE tools. Example: 'If opportunity_id not found, returns 404 with available opportunity IDs. If stage is invalid, returns 400 with valid stage enum values.'
• Add permission declarations to WRITE tools. Example: change_opportunity_stage requires 'write:opportunities' scope. Document in description: 'Requires write:opportunities permission.'