Two tools with minimal descriptions and incomplete parameter documentation. get_task has a 73-char description (below baseline 194 chars); check_pricing has 60 chars. Both tools lack descriptions for optional parameters (action defaults are mentioned but not formally documented). Parameter schemas are present but descriptions are sparse. No output schema documentation visible. Error handling is minimal, no recovery guidance or actionable error messages. Tool names follow verb_noun convention (get_, check_) but descriptions do not explain WHEN to use each tool or what downstream actions they enable.

• Expand tool descriptions to 150 - 250 chars. For get_task: 'Fetch the current status and result payload for an ElevenLabs task created via RunAPI. Use this to poll async operations and retrieve generated audio URLs. Returns task status, output URLs, and error details if failed.'
• Add formal descriptions to optional parameters in schema. For action in get_task: 'Asynchronous endpoint the task was created on (e.g., text_to_speech, isolate_audio). Defaults to the line's only endpoint if only one exists; required if multiple endpoints available.'
• Document output schemas for both tools. Specify what fields get_task returns (task_id, status, result, created_at, etc.) and what check_pricing returns (model, endpoint, price_per_unit, currency, etc.).
• Add error recovery guidance. E.g., 'If task not found, verify task_id is correct. If task is still processing, retry in 5 seconds. If task failed, check error details in the response.'
• Enumerate valid action values in parameter descriptions or via enum constraints. E.g., action: z.enum(['text_to_speech', 'isolate_audio', ...]) with descriptions for each.