Critical gaps across naming, descriptions, and schemas. Tool names lack consistent verb prefixes (e.g., 'wwise_connect', 'ue5_connect' vs. standard 'connect_to_wwise'). Most tools have minimal descriptions (10-30 chars) that fail to explain WHEN to use them or WHAT they return. Input schemas visible for ~10 tools but lack parameter descriptions entirely. No output schemas documented. Error handling absent. Composition issues: tools like 'create_object' and 'create_event' overlap; 'stage_actor' and 'stage_camera' should be unified. No idempotency guarantees, no pagination for list tools, no recovery guidance.

• Expand all tool descriptions to 80-150 characters. Include: (1) what the tool does, (2) when to use it vs. similar tools, (3) what it returns, (4) any prerequisites. Example: 'Create a Wwise Event in the specified parent folder. Returns event_id for use in post_event. Requires wwise_connect to have succeeded.'
• Add parameter descriptions to every input. For enums (object_type, status), list valid values. For strings, specify format/length. Example: 'object_type: Type of Wwise object to create. Valid values: Actor, Event, AuxBus, VirtualVoice, EffectShareSet. Required.'
• Document output schemas for all tools. Specify returned fields, types, and which IDs/references are needed for chaining. Example: 'Returns {event_id: string, parent_path: string, created_at: ISO8601}. Use event_id in post_event or preview_event.'
• Consolidate overlapping tools: merge create_object and create_event into a single create_wwise_object with object_type enum; merge stage_actor and stage_camera into stage_entity with entity_type enum. Reduces LLM confusion and tool count.
• Add error handling with recovery guidance. For each tool, document: (1) common failure modes (connection lost, resource not found, invalid input), (2) whether errors are retryable, (3) what the LLM should do next. Example: 'If event not found, call search_events() with a partial name. If connection fails, call wwise_connect() first.'